Skip to main content

The Rise of Facebook, Part 2: TheFacebook

TheFacebook

📱 The Rise of Facebook — a 20-part series. See all parts »  |  « Part 1: Facemash

Three months after Harvard forced Facemash offline, Mark Zuckerberg was back at his keyboard in Kirkland House — this time building something people would volunteer to join. On February 4, 2004, he registered a modest URL, thefacebook.com, and flipped it live. There was no launch event, no press release, no business plan. Just a login box, a masthead with a blurry face on it, and a promise: a directory of Harvard students, made by students, that you filled in yourself.

It spread like a fever.

TheFacebook's first-year growth timeline

The dorm room that became a company

Zuckerberg didn't build it alone. TheFacebook came together with a small crew of Harvard roommates and friends, each of whom would later be counted among its co-founders. Eduardo Saverin, an economics student with a head for money, put up the first working capital and took on the business side. Dustin Moskovitz, Zuckerberg's roommate, threw himself into the code and the frantic work of adding new schools. Chris Hughes became the product's voice and de facto spokesman, and Andrew McCollum handled graphics — including that hazy face on the early masthead.

What separated it from Facemash was consent. Where Facemash had scraped people's photos to rank them without asking, TheFacebook inverted the whole idea: you signed up, you uploaded your own picture, you listed your year, your classes, your relationship status, your interests. It was a directory people wanted to appear in, because appearing in it — and browsing everyone else — was the entire point. To keep it feeling safe and real, registration required a valid harvard.edu email address. That single constraint did two things at once: it guaranteed real identities, and it made the site feel like an exclusive club.

1,200 sign-ups in a day

The numbers were immediate and absurd. Within the first 24 hours, somewhere between 1,200 and 1,500 Harvard students had registered. Within the first month, more than half of Harvard's undergraduate population had an account. This wasn't a slow-burning experiment that found its audience over a year; it saturated a closed community almost instantly, because a campus is exactly the kind of dense social network where "everyone else is already on it" becomes true within days.

And here was the insight Zuckerberg had been circling since Facemash: people are endlessly fascinated by other people they actually know. Not celebrities, not strangers — the guy from lecture, the girl down the hall, the person you met once at a party. TheFacebook gave that curiosity a safe, addictive outlet, wrapped in the students' own real names and faces.

Jumping the campus walls

Harvard was just the petri dish. By late February 2004 — only weeks after launch — the team began opening the site to other schools, starting with Columbia, Stanford, and Yale, then rolling through the rest of the Ivy League and Boston-area universities that spring. The playbook was deliberate: each new school was its own walled garden, seeded once and left to reach its own tipping point, exactly as Harvard had. School by school, the private club replicated itself.

The growth forced a decision Zuckerberg was already leaning toward. Classes became an afterthought; the site was the real education. By the end of 2004, TheFacebook had roughly one million users — a staggering figure for a product that was, technically, still a side project run by undergraduates.

The shadow over the founding

Not everyone remembered the launch fondly. Months earlier, three other Harvard students — twins Cameron and Tyler Winklevoss and their partner Divya Narendra — had approached Zuckerberg about helping build a campus social network of their own, the project that became Harvard Connection (later ConnectU). They would soon allege that he'd strung them along while quietly building a rival. That dispute would take years, lawyers, and eventually a movie to resolve — but in February 2004 it was still just a grievance, drowned out by the sound of a company being born.

For now, TheFacebook was winning the only contest that mattered: it was the one everybody had actually joined. And the moment Zuckerberg realized how far it could go, he did what every ambitious young founder in that era did next — he pointed the car west.

Next time — Part 3: a summer sublet in Palo Alto, a fast-talking Napster founder named Sean Parker, and the first $500,000 that made it "Facebook."


🔗 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...