Skip to main content

The Rise of Facebook, Part 6: Opening the Platform

Opening the Platform

📱 The Rise of Facebook — a 20-part series. See all parts »  |  « Part 5: Turning Down a Billion

By 2007, Facebook had won its war of features and turned down a billion dollars. It had tens of millions of users and a News Feed that kept them glued to the site. But Zuckerberg wanted something bigger than a website — he wanted a platform, the thing other people build on top of. In 2007 he got his wish twice over: once triumphantly, and once catastrophically.

2007: the Facebook Platform launch and the Beacon backlash timeline

The door swings open

On May 24, 2007, at its first f8 developer conference, Facebook launched the Facebook Platform. The idea was radical for its time: let outside developers build applications that ran inside Facebook, using its data and, crucially, its social graph. A quiz, a game, a music-sharing app — anyone could make one, and any user could add it.

What made the Platform explosive wasn't the apps themselves; it was virality. An app could spread by riding the very channels that made Facebook addictive: friend invitations, notifications, and posts in the News Feed. Install a movie-trivia app and your friends saw it, tried it, and spread it to theirs. Apps like iLike and Causes rocketed from zero to millions of users in weeks — growth curves no standalone website could dream of. Within a year, the Platform hosted tens of thousands of applications built by hundreds of thousands of developers. Facebook had turned itself from a destination into an economy. (It also, less gloriously, unleashed a plague of app-invite spam — but that was a problem of abundance.)

This was the blueprint Zuckerberg would follow forever: own the graph, then let everyone else build on it. It's the same instinct that later made mobile, and then AI, existential priorities. But 2007 also taught him — the hard way — exactly where the line was.

Beacon: the bet that backfired

Facebook needed to make money, and Zuckerberg had a theory that would define the next fifteen years: the most powerful advertising isn't an ad at all — it's your friends' behavior. On November 6, 2007, Facebook launched Beacon, a system that partnered with 44 external websites — Fandango, Overstock, Blockbuster and others. When you bought a movie ticket or a product on a partner site, Beacon reported it back to Facebook and broadcast it into your friends' News Feeds: "Alex bought this on Overstock."

The problem was consent — there wasn't any. Purchases showed up in feeds by default, and reporting happened even when users weren't logged in and hadn't agreed. The now-legendary horror story: a man's secret purchase of a diamond ring was announced to his wife by Facebook, spoiling the surprise. People were furious, and rightly so.

50,000 signatures in ten days

The backlash was immediate and organized. On November 20, 2007, the civic group MoveOn.org launched a petition demanding Facebook stop publishing off-site activity without explicit permission. It drew 50,000 members in under ten days. Worse, a security researcher soon demonstrated that Beacon was still collecting data even from users who had opted out and logged off — directly contradicting Facebook's public assurances.

Faced with the first real revolt of the paying era, Zuckerberg did something he'd get better at over the years: he apologized. On December 5, 2007, he posted, “We simply did a bad job with this release, and I apologize for it.” Facebook made Beacon opt-in, then gave users a way to turn it off entirely. It wasn't enough. A class-action suit, Lane v. Facebook, followed, and Beacon was quietly shut down in September 2009. Years later, Zuckerberg would flatly call it a “mistake.”

But the underlying conviction never died. Beacon failed because it took people's data without asking — not because Zuckerberg was wrong that social behavior was advertising gold. That idea would come back, done far more carefully and far more profitably, the moment the right executive walked through the door. She was about to.

Next time — Part 7: in 2008, Sheryl Sandberg leaves Google for Facebook and builds the advertising machine that finally makes it profitable.


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