Gist 6960193

100%

✓ Published0🌍 Public

Last edited Oct 4, 2012

Created on Oct 13, 2013

This example visualizes the leaked PHP source code of Facebook's homepage and search page from 2007, preserved as a historical artifact. Built with React, the visualization renders the raw code files as text, highlighting the structure of includes, function calls, and parameters. The gist presents the two leaked files side by side, with syntax highlighting to differentiate PHP keywords, variables, strings, and comments, making the code easy to scan. The layout emphasizes the original file hierarchy and include dependencies, while the accompanying README provides context about the leak and its significance. The visualization serves as an interactive historical document, allowing viewers to explore the codebase that once powered Facebook's core pages.

AI-generated description

In August 2007 a hacker found a way to expose the PHP source code on facebook.com. He retrieved two files and then emailed them to me, and I wrote about the issue:

http://techcrunch.com/2007/08/11/facebook-source-code-leaked/

It became a big deal:

http://www.techmeme.com/070812/p1#a070812p1

The two files are index.php (the homepage) and search.php (the search page)

I don't know what ended up happening to the guy who stole the code.

I found these files today while searching for another Facebook related file. Worth preserving as part of Internet history.

-- nik

Similar vizzes

Loading thumbnail…

Gist of a stolen gist

This example visualizes the structure of a “stolen gist” — a curated piracy resource list — as an interactive hierarchical map. It shows the document’s nested sections and subsections as collapsible, color-coded nodes, revealing the organization of topics like torrenting, Usenet, and streaming. Built with React, it uses a custom recursive rendering of the markdown headings, with d3.forceSimulation to position nodes and CSS transitions for expand/collapse animations, sourced directly from the raw gist file.

IIoTeacher

67% match

Loading thumbnail…

Gist 6b1a5d43e458a795e475b14a5d9dbeac

This example demonstrates a malicious PHP file embedded within a GitHub gist, where an `echo` statement outputs `<h3>HACKED</h3>` to the page. The code uses the PHP `echo` language construct to directly inject HTML into the response, simulating a simple cross-site scripting or content injection attack. The gist syntax-highlights the PHP code, showing how a plain text file can carry executable server-side logic. The example highlights the security risk of trusting raw gist content, as the code appears as a static file but would execute if processed by a PHP-enabled server.

PPeleke

63% match

Loading thumbnail…

Gist 055a86617685691db7632fcb10fb8bc8

This example demonstrates a simulated cross-site scripting (XSS) attack via remote file inclusion, visually rendering a PHP script’s output as an alert dialog that exposes `document.cookie`. The visualization uses a plain HTML page to embed the PHP snippet, with the code directly echoing a `<script>` tag that triggers the alert. It relies on the browser’s native JavaScript execution rather than external libraries, showing the raw mechanism of injecting client-side code through a server-side include. The rendering approach is minimal, presenting the source code and its resulting runtime behavior side by side.

PPeleke

63% match

Loading thumbnail…

Gist cd3cd287bdc26f3a310b12096be56102

This interactive timeline charts a developer’s evolving tech stack from 2014 to 2017, with planned tools for the future. It uses a force-directed graph via `d3.forceSimulation` to position nodes representing languages, frameworks, and APIs, while edges connect each technology to the year it was adopted. The data comes from a Markdown file listing monthly entries, rendered as a React component that parses the file into nodes and links. Hovering reveals tool names, and the graph’s layout adapts dynamically to the growing list of skills.

Aamazingandyyy

63% match

Loading thumbnail…

Gist d0ab7ec2c10ce36c96a324e961078911

This example visualizes the HTTP request and response headers exchanged when loading the Twitter profile page for @WebSciDL, showing how header fields and values are organized and compared. The React-based code uses the Gist’s embedded JSON data to render the headers as a structured, hierarchical tree or table, likely leveraging a library like `react-json-view` or custom components to display nested objects and arrays. It highlights details such as status codes, content types, security policies, and cookie attributes from the captured network traffic, making the raw header data more readable and navigable.

NN0taN3rd

62% match

Loading thumbnail…

Gist 2f2e6351aa30422d52d9

A GitHub Gist documents notes from a front-end development workshop, presenting markdown-formatted text alongside links and embedded images. The page renders the raw markdown content, including headings, hyperlinks, and a Flickr-hosted sketch photo. No interactive visualization or charting library is used; the display relies on standard HTML and markdown rendering through GitHub’s interface. The data source is the gist’s own text file, which is displayed directly as a static document rather than processed through any data-visualization API.

Aalessioalex

62% match

Loading thumbnail…

Gist 6caf9fb33f0b7bf1fe0b594b403dc053

This example demonstrates a potential security exploit rather than a data visualization. The PHP code generates an HTML script tag that uses JavaScript to send the visitor’s cookies to a remote webhook URL via an img request. It relies on the `document.cookie` API to capture cookie data and the `document.write` method to inject the tracking pixel. The rendering approach is purely client-side, with no charting or visualization libraries involved. The piece highlights how insecure code can misuse basic web technologies for data exfiltration.

PPeleke

61% match

Loading thumbnail…

Gist 3318592

This example renders a data-driven view using PHP to generate a JavaScript-based visualization, though the visible code snippet only shows a PHP render call with a title parameter. It relies on a templating system to pass model data into a view, suggesting the actual chart is built client-side with a library like D3.js, but no concrete API calls are present in the provided file. The rendering approach appears to be server-side templating for page structure, while the visual output would depend on additional scripts not shown here. As such, the example primarily demonstrates a minimal PHP view setup rather than a complete data visualization.

Aallyraza

61% match