Summary
Journalists are increasingly abandoning X (formerly Twitter) for Bluesky, citing higher engagement and less toxicity. Since Elon Musk’s takeover of X, changes like deprioritizing external links and rising hate speech have alienated many, especially marginalized groups.
Bluesky, founded by Jack Dorsey, offers a more welcoming environment, especially for journalists and activists, with 20x the engagement in some cases.
Reporters note better traffic, reduced harassment, and a focus on diverse stories.
Organizations like The Guardian and fundraising groups also report greater success on Bluesky compared to X.
Phew … then we can trust the open software that is locked to one company and one instance essentially leaving control to a handful of people.
What could go wrong?
I’m not saying open software isn’t awesome. I’m simply correcting a common misconception.
I agree, there is nothing wrong with Open Software … the problem is the way Bluesky is being arranged and developed. They are essentially cornering the development to create a situation where only one company and one group maintains dominate control over everything and everyone.
The track record so far since the popular world wide internet started is that if a popular social media platform is controlled by one group, one company or even one person, it will eventually turn into a tool of monetization and control and it will eventually degrade and dissolve.
The only difference this time is Bluesky is supposedly built on open source software, which is true … but the whole platform and system is corned, controlled and managed by only one company and one group.
They’re actively working on making it easier to fork the entire platform.
There’s already 3rd party account hosts, moderation labelers, feed generators, and alternative implementations like whitewind (blogging system on top of the same account repo & lexicon architecture) were you can use the exact same account. All of these works together independently of which hosts / providers you use.
Relays and microblogging appviews (a fully functional bluesky mirror) are technically possible but more expensive to duplicate but there’s work on making that practical too.
You can already bypass PLC by using DID:Web for account identity.
The single most important thing if you want to be able to recover from bluesky going bad is to just back up your account recover signing key, and to keep a recent backup of the repo to preserve your post history and social network (follows, etc).
All the rest can be rebuilt if you have your account hey and backup. The content addressing will make it seamless!
