Bluesky's sudden surge—from 15 million to 16 million users in November—tells a more interesting story than raw numbers suggest. The spike wasn't organic enthusiasm but reaction: Threads' suppression of political content, moderation errors blanking accounts, and the discomfort of seeing Elon Musk align openly with Trump's government all pushed people elsewhere. The Guardian's departure from X crystallized something larger: a platform owner's political positioning had become too intrusive to ignore.
But Bluesky isn't just Twitter's nostalgia mirror. Its architecture and emerging features reveal a different model. The protocol runs on ActivityPub, the same federated standard Threads and Mastodon use, meaning posts can theoretically flow between platforms. More radically, Bluesky's Ozone system lets users and organizations build custom moderation algorithms—filtering by ideology, topic, or quality threshold—that they can adopt for their feed. You aren't choosing between "algorithm" or "no algorithm"; you're choosing which algorithm. This matters. No institution decides what you see; you do.
The tradeoff is real. Algorithmic choice enables ideological bubbles you construct yourself. But as the host notes, a bubble you build knowingly differs from one built by Instagram and hidden behind proprietary code. Meta's approach to political content—throttling reach by default—amounts to invisible curation. Bluesky's approach is explicit: curate or don't, but own the choice.
The engagement metrics are telling. Bluesky maintains a 30% posting rate among active users; Twitter's 99/1 rule—90% lurkers, 1% posters—hasn't yet reasserted itself. This won't last. Scale kills participation. But for now, Bluesky resembles early Twitter: distributed, high-friction, full of people who actually have something to say.
The platform raised $15 million in pre-seed funding and plans subscriptions and ads. It will need revenue. The real question isn't whether Bluesky survives but whether the federated model—where platform choice becomes UI preference rather than network trap—becomes the default. Threads, Mastodon, and Bluesky already interoperate to degrees. If that model holds, the power asymmetry between user and platform collapses. You post once; you read everywhere.