c/technology · by Hotznplotzn@lemmy.sdf.org · 1y

Bluesky will trap academics in the same way Twitter/X did

https://blogs.lse.ac.uk/impactofsocialsciences/2025/03/03/bluesky-will-trap-academics-in-the-same-way-twitter-x-did

cross-posted from: https://lemmy.sdf.org/post/30464375

[...]

Bluesky is built on a protocol intended to mitigate this problem. The AT Protocol describes itself as “an open, decentralized network for building social applications”. The problem is that, [...] “A federatable service isn’t a federated one”. The intention to create a platform that users can leave at will, without losing their social connections, does not mean users can actually do this. It’s a technical possibility tied to an organisational promise, rather than a federated structure that enables people to move between services if they become frustrated by Bluesky.

[...]

The problem is that, as Doctorow observes, “The more effort we put into making Bluesky and Threads good, the more we tempt their managers to break their promises and never open up a federation”. If you were a venture capitalist putting millions into Bluesky in the hope of an eventual profit, how would you feel about designing the service in a way that reduces exit costs to near zero? This would mean that “An owner who makes a bad call – like removing the block function say, or opting every user into AI training – will lose a lot of users”. The developing social media landscape being tied in the Generative AI bubble means this example in particular is one we need to take extremely seriously.

[...]

110 points · 13 comments · view on lemmy.world

13 Comments

HubertManne@moist.catsweat.com · 21 pts · 1y (3 replies)

universities and other orgs should do their own federated servers. they should also take back and manage their email if they let a third party handle it.

obbeel@lemmy.eco.br · 2 pts · 1y (1 reply)

Is this possible on Bluesky?

HubertManne@moist.catsweat.com · 8 pts · 1y

not in the way im talking. I want them to take back their infrastructure and control it themselves and not under someones umbrella.

possiblylinux127@lemmy.zip · 1 pts · 1y

That seems like a bad idea

unexposedhazard@discuss.tchncs.de · 14 pts · 1y (1 reply)

Bluesky enshittification has already started. You needed 3rd party clients to use it properly from day one and they have central control over the whole platform. It will only take some politically controversial event and they will quickly show their true colors.

reseller_pledge609@lemmy.dbzer0.com · 5 pts · 1y

And most users will move to the next closed platform again.

The average user just doesn't learn from this shit because they don't know.

p03locke@lemmy.dbzer0.com · 8 pts · 1y

The more effort we put into making Bluesky and Threads good

While I somewhat agree, I don't think we should be putting "Bluesky" and "Threads" in the same sentence.

Also, I think Threads is a cautionary tale around this whole protocol argument, where a federated technology does not automatically mean it's safe.

kandoh@reddthat.com · 8 pts · 1y (5 replies)

People did originally move to Mastodon, but they got tripped up when they had to select a server and the whole exodus failed until bluesky opened up.

p03locke@lemmy.dbzer0.com · 2 pts · 1y (3 replies)

I still don't understand why that's the barrier to entry for many people. It's like people want to be enslaved to a monopoly on purpose.

yhvr@lemm.ee · 3 pts · 1y

In case it helps you understand: barriers of entry to Mastodon, from my perspective as an ex-Twitter user and current Bluesky and Mastodon user (note it took me 4 tries over 5 years to actually "enjoy" Mastodon)

Lack of content discoverability: Bluesky has programmable feeds and starter packs (although the latter is pretty flawed), Twitter has The Algorithm. When you first create a Mastodon account, you're not given much.
- The primary reason Mastodon "stuck" with me on the 4th go around was this. I manually imported a bunch of my connections from Bluesky.
Choosing the right server: on all my previous attempts, I was overwhelmed by server selection and went with generic all-purpose instances. Having a local timeline with things that might actually interest you is very helpful.
The network effect: I don't think I really have to elaborate on this one

Bonus things that probably don't serve as barriers to entry but are real issues for active users:

Lack of features: it's not possible to search for posts on ActivityPub at any reasonable scale. I don't know all my Mastodon lore and think I've heard that search was intentionally not made good in the past for privacy or something, but if you're posting something on the "blast my posts everywhere" protocol, well... it's still out there.
- There's also no quote posts, which haven't been implemented for similar privacy/anti-harassment reasons. But instead, other software like Pleroma works around this by simply giving a link to the original post—the worst of both worlds, bad UX and not even an option to attempt to detach or prevent quotes.
Fedi meta / sudden defederations: If you picked the wrong server—or any of your friends did—and you end up with a tempermental admin, you could unexpectedly lose contact with each other due to defederation, and you might not even notice.

This is not to say other platforms are perfect. There are plenty of things I don't like about Bluesky. This comment is specifically about Mastodon.

possiblylinux127@lemmy.zip · 3 pts · 1y

Because it has a huge impact on the user experience. You primarily see content from the home server.

kandoh@reddthat.com · 1 pts · 1y

People saw the servers and it reminded them of how world of warcraft worked

possiblylinux127@lemmy.zip · 2 pts · 1y

The concept of home server in Mastodon is not great. I think servers should show content from all over Mastodon with most servers giving the same experience. Expecting people to pick a server and then mostly talk to the same people is silly.

Lemmy is much better in that regard since content is organized by community.