Skip to main content

The Rise of Facebook, Part 1: Facemash

Facemash

📱 The Rise of Facebook — a 20-part series. See all parts »

Every empire has an origin myth, and Facebook's begins not with a grand vision of connecting the world, but with a petty, sleep-deprived act of revenge against a database of student photos. On the night of October 28, 2003, a 19-year-old Harvard sophomore named Mark Zuckerberg sat in his Kirkland House dorm room, cracked open a beer, and started building a website that would nearly get him expelled — and would quietly rehearse every instinct that later made him a billionaire.

The site was called Facemash. The premise was crude: put two Harvard students' photos side by side and ask visitors a single question — who's hotter? The homepage announced its own thesis with a shrug: “Were we admitted for our looks? No. Will we be judged by them? Yes.”

Facemash launch-night statistics

A night of coding, documented in real time

What made Facemash notable wasn't the idea — “hot or not” sites already existed — but how Zuckerberg got the raw material. Harvard's residential houses each kept an online directory of student ID photos, informally called “facebooks.” There was no single university-wide version, and the individual ones were locked behind house logins. So Zuckerberg simply took them. He wrote later, in a blog he kept open while he worked, about hacking into the house intranets one by one and scraping the images. Some he grabbed with borrowed credentials; others he pulled through gaps in the sites' security. He even mused, half-jokingly, about pitting students against farm animals before thinking better of it.

The whole thing came together in a matter of days — the actual build, by his own account, in a single feverish stretch. He wrote the code, wired up an algorithm to rank faces using a chess-style rating system, and pushed it live to a few friends, expecting it to stay a private joke over the weekend.

450 students, 22,000 votes, and a crashed network

It did not stay private. The link ricocheted through Harvard's email lists within hours. By the end of that first day, the site had drawn roughly 450 visitors who cast at least 22,000 votes on the paired photos. That was enough traffic to bog down the Harvard network segment it was running on — a college prank generating server load usually reserved for real products.

It was also enough to enrage a lot of people, for good reason. Students discovered their ID photos were being ranked for attractiveness without their knowledge or consent. Campus groups including Fuerza Latina and the Harvard Association of Black Women objected, raising concerns about privacy and about singling people out by looks. Within days — some accounts say hours — Zuckerberg pulled the plug himself as the backlash mounted.

Hauled before the Ad Board

Harvard was not amused. Zuckerberg was summoned before the university's Administrative Board and faced accusations that boiled down to four charges: breaching computer security, violating copyrights, and violating individual privacy (the photo misuse counted twice over). Expulsion was on the table. He apologized publicly, particularly to the groups he'd offended, and in the end the university let him stay — the charges were dropped. He remained a student at Harvard for another year and a half before leaving to build the thing Facemash had foreshadowed.

Because that's the real significance of Facemash: not the misogyny or the mischief, but the pattern. In one weekend, Zuckerberg demonstrated the exact playbook he'd run for the next two decades. He saw that people were magnetically drawn to content about other people they knew. He built fast and shipped before asking permission. He treated data that wasn't his as raw material. And he learned, viscerally, that a simple social mechanic could spread through a real-world community faster than any advertising ever could.

The idea underneath the prank

In the weeks after Facemash came down, a genuinely useful thought surfaced from the wreckage. Harvard, students noted, still had no unified online directory — no single place to look up a classmate, see their photo, their year, their interests. The administration had talked about building one for years and kept stalling over privacy worries. The very worries Facemash had just trampled.

Zuckerberg took the lesson. If people would flock to a site just to rank each other's faces, imagine what they'd do with a site built around their real identities — one they populated voluntarily, that let them present themselves rather than be judged. A directory people wanted to be in. He registered a domain in January 2004 and started coding again.

The prank had lasted a few days. What it taught him would build a company worth more than a trillion dollars.

Next time — Part 2: TheFacebook goes live in February 2004, and a dorm-room directory starts jumping from campus to campus.


🔗 Explore more from Syncster

Comments

Popular posts from this blog

Cursor AI Review: Is the AI Code Editor Worth It?

I've been using Cursor as my main code editor for a while now, and enough people have asked whether it's worth switching to that a proper review felt overdue. Short version: for me, yes — but with caveats. What is Cursor? Cursor is an AI-first code editor built as a fork of VS Code. That means every extension, theme, and keybinding you already use in VS Code works here, but with AI woven directly into the editing experience instead of bolted on as a plugin. It's made by Anysphere and can run models from OpenAI and Anthropic under the hood. What I like Tab completion is uncanny. Cursor predicts your next edit — not just the rest of the line, but the next change across the file. Once you get used to hitting Tab, going back to a plain editor feels slow. The Composer / Agent mode. You describe a change in plain language and it edits multiple files at once, showing you a diff to accept or reject. For refactors and boilerplate, this saves real time. It unde...

MacBook Pro M5 vs M5 Pro: Which One Should You Actually Buy?

Apple's latest 14-inch MacBook Pro comes in two very different flavors: the base M5 and the step-up M5 Pro . On paper they look similar — same gorgeous Liquid Retina XDR display, same design — but under the hood the gap is bigger than the names suggest. Here's a clear, no-hype breakdown, with concrete use cases so you can match the chip to your work. Quick spec comparison Spec M5 M5 Pro CPU 10-core (4 performance + 6 efficiency) Up to 18-core (6 performance + 12 efficiency) GPU 10-core Up to 20-core Neural Engine 16-core 16-core Memory bandwidth 153 GB/s 307 GB/s (roughly double) Unified memory 16 / 24 / 32 GB 24 / 48 / 64 GB Max storage Up to 4 TB SSD Up to 8 TB SSD Battery (video playback) Up to 24 hours Up to 22 hours Media engines Single encode/ProRes engine More encode/ProRes engines (higher configs) What actually changes between them More cores — the M5 Pro nearly doubles CPU cores and adds GPU cores, so sustained, multi-threaded work finishe...

Running a Server on a Mac Mini: Apple Silicon vs the Home-Server Field

The Mac Mini has quietly become one of the most interesting home-server boxes you can buy. It’s tiny, nearly silent, sips power, and Apple Silicon punches far above its weight. But is it actually the right machine to run your services on — or are you paying an Apple tax for a job a $400 mini PC does better? Let’s put it head-to-head. Why a Mac Mini makes a surprisingly good server Three things make Apple Silicon compelling as an always-on machine: Performance per watt. This is the headline. An M4 Mini idles at just a few watts and rarely pushes past ~35W under load, while delivering multicore performance that embarrasses machines drawing twice the power. Silence. Under typical server loads the fan is inaudible. If your “server” lives in a living room or bedroom, this matters more than any benchmark. Footprint. It’s the size of a coaster and runs cool, so it tucks anywhere. The honest catch It’s not all upside: macOS isn’t...