Skip to main content

The Rise of Facebook, Part 4: The News Feed Revolt

The News Feed Revolt

📱 The Rise of Facebook — a 20-part series. See all parts »  |  « Part 3: Dropping the 'The'

On the morning of September 5, 2006, Facebook users logged in expecting the same quiet, page-by-page site they had always used. Instead they got a scrolling river of everything their friends had just done: who added whom, who broke up, who joined a group, who changed a photo. Facebook called it the News Feed. Users called it something closer to a violation. Within hours, the friendliest college site on the internet was in open revolt against the company that ran it.

The feature nobody asked for

Up to that point, Facebook was a collection of profiles you had to go and visit. If you wanted to know what a friend was up to, you clicked to their page and looked. The News Feed flipped that on its head. Now the home screen aggregated your friends' activity automatically, timestamped and ranked, and pushed it in front of you the moment you logged in. A companion feature, the Mini-Feed, did the same thing on each individual profile, logging a running history of that person's recent changes.

Nothing about the underlying information was actually new. Every item in the feed was already visible somewhere on the site — a relationship status, a wall post, a new friend. Facebook's engineers saw the feed as a convenience: instead of hunting through dozens of profiles, the news came to you. But convenience wasn't the problem. The problem was exposure. Information that had technically been public suddenly felt broadcast. Breaking up with someone was one thing; having it announced to hundreds of classmates in a tidy, timestamped headline was another entirely.

Half a million angry students

The backlash organized itself with terrifying speed — on Facebook, using Facebook's own tools. A junior at Northwestern University named Ben Parr logged in, recoiled at the new feed, and created a group called "Students Against Facebook News Feed (Official Petition to Facebook)." He told a few friends and walked away from his computer. When he came back a few hours later, the group had roughly 13,000 members. By 2 a.m. it had crossed 100,000. Within days it swelled past 700,000 people — somewhere around seven percent of Facebook's entire user base at the time — with something like 500 new members joining every minute at the peak.

It was, in a strange way, a perfect demonstration of exactly why the News Feed was powerful. The same viral, friend-to-friend mechanics that made people furious were the mechanics spreading the protest. Students threatened boycotts. Reporters at the Harvard Crimson and TechCrunch chronicled the meltdown in real time. The complaint was consistent: the feed was too intrusive, too detailed, too much like surveillance. Facebook, still a company of a few dozen people, had shipped a feature that made a huge chunk of its users feel watched.

Calm down. Breathe.

Facebook's first response was a blog post from Mark Zuckerberg with a title that has since become internet lore: "Calm down. Breathe. We hear you." In it, the 22-year-old CEO argued that no privacy settings had actually changed and that the feed only surfaced things users had already shared. It was technically accurate and completely tone-deaf. Telling hundreds of thousands of upset people to calm down rarely calms anyone down.

The turning point came a few days later, on September 8. Zuckerberg posted a genuine apology — "We really messed this one up," he wrote, admitting the company "did a bad job of explaining what the new features were and an even worse job of giving you control of them." Crucially, the apology came bundled with action: Facebook rolled out a new set of privacy controls that let users decide what showed up in the feed and what stayed off it. The company didn't kill the News Feed. It kept the feature and handed users the dials.

That decision defined the pattern Facebook would repeat for the next decade. Ship something disruptive, absorb the outrage, apologize, add controls — and keep the feature. Because here is the part that still surprises people: the same users who signed the petition kept using the feed, and used the site more. Time on Facebook climbed. The News Feed, so hated in its first week, quietly became the reason people opened the app at all. Within a couple of years it was the single most-viewed surface on the internet, and the foundation on which Facebook would later build its entire advertising empire.

The revolt of September 2006 turned out to be a preview of the company's whole future: a repeated collision between what Facebook could show people and what people were comfortable being shown. And it ended, as those collisions usually would, with Facebook getting its way — just with better controls and a public apology stapled on. Later that same month, on September 26, the company opened registration to anyone thirteen and older with an email address, blowing the doors off the college-only walled garden entirely.

Next time: the gates come down. Facebook opens to the whole world, and a scrappy campus network sets out to swallow the internet.


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