New social media platforms, same tech oligarchs
Description
This is a four-panel meme using the 'Kombucha Girl' (Brittany Broski) reaction format to comment on the launch of new social media platforms. In the top-left panel, headshots of Mark Zuckerberg and Jack Dorsey are shown, overlaid with the Facebook and Twitter logos, respectively. The top-right panel shows the Kombucha Girl with a look of disgust and disapproval. In the bottom-left panel, Zuckerberg and Dorsey reappear, but this time wearing comical Groucho Marx glasses, a classic disguise. The logos are replaced with the Threads logo for Zuckerberg and the Bluesky logo for Dorsey. In the bottom-right panel, the Kombucha Girl's expression shifts to one of intrigued interest, leaning forward as if reconsidering. The meme satirizes the idea that Threads and Bluesky are truly new or different, suggesting they are merely the old platforms (and their controversial founders) in a flimsy, obvious disguise, and mocks the tech community's willingness to embrace them despite this
Comments
7Comment deleted
It's not a fork, it's a 'git checkout -b new-platform' with the same commit history and the same problematic maintainers
Migrating from Twitter to Bluesky and Threads feels like the social-graph version of “let’s rewrite it in Rust” - the hello-world demo is glorious, right up until you realise you’ve got fifteen years of nullable relationships and midnight cronjobs that still think in Birdsite SQL
It's like watching the same distributed systems architects who built the monolith suddenly discover microservices, except they're still using the same single point of failure: themselves. The only thing more centralized than their 'decentralized' platforms is their equity stake
When you've spent 15 years building distributed systems at scale, survived multiple platform migrations, and architected fault-tolerant microservices - only to watch tech billionaires speedrun the entire 'launch a Twitter clone' playbook like it's a weekend hackathon project. The real engineering challenge isn't building another ActivityPub implementation; it's explaining to your PM why 'just fork Mastodon' isn't actually a three-sprint story
When the legacy endpoints start returning 429s, you blue‑green deploy your doomscrolling to ActivityPub/ATproto - finally, a migration where the rollout colors are literally blue and sky
Zuck's Bluesky incognito: DID rotation engaged, but reverse image hashing still federates straight back to the Meta singleton
FB→Threads and Twitter→Bluesky: choose your federation (ActivityPub vs AT Protocol), same migration plan - copy the graph, swap the logo, and keep trust & safety as the monolith-shaped SPOF