Skip to main content

The Rise of Facebook, Part 8: The Social Network

The Social Network

📱 The Rise of Facebook — a 20-part series. See all parts »  |  « Part 7: Enter Sheryl Sandberg

By 2008, Facebook had a hit product, a booming ad business, and a brand-new chief operating officer. What it did not have was a clean origin story. The question that had trailed Mark Zuckerberg since his Harvard dorm room — whose idea was this, really? — was about to be answered twice: once by a courtroom, and once, far more memorably, by Hollywood.

Two lawsuits, one question

The first challenge came from three fellow Harvard students. In December 2002, Cameron Winklevoss, his twin brother Tyler, and their friend Divya Narendra had begun sketching a campus social network they called HarvardConnection (later ConnectU). In November 2003 they recruited a sophomore programmer to help finish it: Mark Zuckerberg. Weeks later he stopped returning their messages — and in February 2004 launched TheFacebook instead. The Winklevosses claimed he had stolen their idea and stalled them on purpose.

Years of litigation followed. In 2008, the two sides settled. Facebook agreed to pay roughly $65 million — about $20 million in cash and the rest, some $45 million, in Facebook stock. It was a fortune, but the Winklevosses came to regret the shape of the deal. They argued the shares had been valued too high, effectively shrinking what they received, and tried to reopen the case. In 2011 a federal appeals court shut the door. “At some point,” wrote Judge Alex Kozinski, “litigation must come to an end. That point has now been reached.” Ironically, the stock they resented would later balloon in value, quietly making the settlement one of the better paydays of the whole saga.

The second challenge came from closer in. Eduardo Saverin was Zuckerberg’s original business partner and the friend who put up the first real money to keep the site running. But as Facebook restructured and took on investment, new shares were issued and Saverin’s ownership was diluted from a meaningful slice to a sliver. He sued. The terms of their settlement stayed confidential, but the visible result was telling: Saverin was formally restored to the story as a co-founder, his title reinstated on Facebook’s own pages.

The movie that rewrote the myth

If the lawsuits settled the legal questions, they did nothing to settle the public one. That job fell, improbably, to a feature film. In 2009 writer Ben Mezrich published The Accidental Billionaires, a dramatized account built partly on Saverin’s cooperation. Screenwriter Aaron Sorkin turned it into a script, and director David Fincher turned the script into The Social Network, released in October 2010.

It was not the movie anyone expected a website to inspire. Jesse Eisenberg played Zuckerberg as a brilliant, wounded striver; Andrew Garfield played Saverin as the loyal friend cut out of the deal; Justin Timberlake played Napster co-founder Sean Parker as the charming devil on Zuckerberg’s shoulder; and Armie Hammer played both Winklevoss twins. Made for about $40 million, it earned some $225 million worldwide and swept awards season — eight Academy Award nominations, three wins (Adapted Screenplay, Original Score, and Film Editing), plus the Golden Globe for Best Drama.

Crucially, the film framed the birth of Facebook as a story of betrayal and social insecurity — a boy building a global network because he couldn’t get a girl or a spot in a Harvard final club. It was gripping. It was also, Zuckerberg insisted, wrong.

The myth versus the man

Zuckerberg’s public response was pointed but dry. The filmmakers, he noted, got the surface details right — even his actual wardrobe of T-shirts, hoodies, and sandals — while inventing the motive. “They just kind of made up a bunch of stuff that I found kind of hurtful,” he said, adding that the idea he built Facebook to impress people or join clubs missed the truth: he and his friends simply liked building things. The most revealing line came later, and he made it flattering by accident — the movie, he said, got the clothes and the code right and the reason completely backwards.

Whatever its accuracy, the film did something no press release could: it fixed a version of Facebook’s founding in the public imagination. A generation now “knows” the story through Sorkin’s dialogue, not the court filings. And there was a strange business upside. Just as the movie painted Zuckerberg as ruthless, it also cemented him as a defining figure of his era — a 26-year-old whose company was interesting enough to dramatize. Myths, it turns out, are their own form of marketing.

The lawsuits closed the books on who could claim a piece of Facebook. The movie decided how the world would remember it. Neither slowed the company down for a moment — because while the courts and cameras looked backward, Facebook was busy racing toward a number no social network had ever reached.

Next in the series: “Move Fast and Break Things” — the growth machine that pushed Facebook past half a billion users.


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