I just received my invite code today and took a quick look around the app. Like Mastodon I do not prefer microblogging platforms. And that’s all I know about Bluesky.
So, what can you tell me about this project?
I just received my invite code today and took a quick look around the app. Like Mastodon I do not prefer microblogging platforms. And that’s all I know about Bluesky.
So, what can you tell me about this project?
A few podcasts I listen to have switched to calling their bluesky handles out instead of their twitter handles in their outros. I’ll probably install it and delete ex/twitter when I get an invite.
Go with Mastodon. Bluesky is just Twitter but run by crypto fanatics. It’s not decentralized or nonprofit or safeguarded against enshittification.
They’re not cryptocurrency fanatics. None of the project relies on cryptocurrency tech. Even Jack himself deleted his account and ran off to nostr.
Bluesky uses a model with user identities based on cryptographic keypairs, posts held in a personal account repository (git-like), and posts use content addressing (hash ID of posts), and everything is portable so you can move your account between host servers without breaking any references.
Federation is up in the sandbox environment with 3rd party implementations participating.
It’s more robust against enshittification than your average Mastodon server
I’m very skeptical of that. What makes Mastodon so robust against enshittification is that it’s hard for a single or small set of players to have so much control that they can act as gatekeeper to extract money from the user base.
Blue Sky is a for-profit corporation. How do they plan to make money? Who controls access to the network? These are genuine questions.
🤷
They use domain names for handles, they do have a partnership with one registrar for integration for users who want custom domains for handles (commission model). Other than that, to be seen.
Once full federation is live, nobody. Anybody could create a relay server (BGS, shared cache server like a CDN), and anybody can run a PDS (account hosting server).
3rd parties already run feeds on their own servers and 3rd party clients exists, and the sandbox network for federation testing has 3rd party PDS servers too.
For user account lookups, if you use the web-DID type then you’re not dependent on bluesky servers at all.
Account portability and the ability to mix and match services and switch quickly are the biggest enshittification protection mechanisms. You can’t really lock in users in this model. You can’t even prevent users from ditching your PDS account host if they kept a backup of their data and held their own keys.
Thank you for the response. Alas, the monetization question is key to enshittification. I’m left unassuaged.
Let’s take a concrete example. There are a bunch of neo-nazis inciting real violence on Blue Sky. People will die. Does anyone have the power to do anything about them? Or can the neo-nazis " mix and match services and switch quickly" to escape any consequences? It’s a dilemma either way. On one fork, BS has no control, which means bad actors run free. On the other fork, BS does have control, which suggests they’re not as enshittification resistant as it may seem.
I know and am happy with how Activity Pub (Lemmy/Mastodon) deals with both forks, as imperfect as the system is. What about Blue Sky?
Yeah, with no strong central control the best you can do is to persuade PDS account servers and client developers to put in good moderation filters by default, so that the average user won’t have to see that stuff assuming they land on a client/server which filter it. You can’t stop it from existing in the network, but you can coordinate ways to inhibit reach. And users who need even better tools can deploy them without having to move.
On the other hand, the work on private profiles haven’t started yet, and you can’t currently prevent yourself from getting visible to others.
On Mastodon the options are essentially just finding a server with a good moderation team and importing block list files manually, as well as keyword filters. And that’s pretty much it. The server features and moderation quality are part of the same bundle.
@Natanael enshittification is about power, and ATproto is designed to look decentralized but enable secondary centralization where it matters for power dynamics in the network, in a way that the Fediverse very much doesn’t:
https://rys.io/en/167.html
(shameless plug, I wrote that, but it dives somewhat deep into the “why” of what I said above)
tl;dr it doesn’t matter which PDS you use if everyone is still beholden to the same entity that controls the “reach” layer in BS.
@SkepticalButOpenMinded
https://slrpnk.net/comment/3996311
You’re missing details
The Mastodon fediverse have stronger network effects because big servers can enforce policies on other servers to stay federated. It’s complicated for users to move servers.
In Bluesky you have plenty more options, including using 3rd party moderation, using clients which can pull censored posts from other servers and cleanly render them into threads, and you can move servers much more easily even if the server operator don’t want to let you.
The “reach” layer is a mix of relay servers (BGS) and 3rd party feeds (which already are operated independently)
@Natanael
> The Mastodon fediverse have stronger network effects because big servers can enforce policies on other servers to stay federated. It’s complicated for users to move servers.
Well, I wrote about this as well, so I think I might not be missing these details:
https://rys.io/en/168.html
In bluesky I think those effects mostly lie on the side of which client people use.
The protocol is extensible and you can add new post types and formatting options by creating a new schema/lexicon, but these would only be readable by other clients which supports it. I hope they’ll be able to add some general “category template” lexicons so a graceful degradation scheme can be implemented to support compatibility without hindering 3rd party development.
To protect against a PDS server going bad the client could assist with automated account migration (the new PDS doesn’t need to understand the lexicon of your posts to be able to migrate them intact), even if the old PDS won’t cooperate (the client could maintain backups for you to make migration quick). But if you don’t control your keys separately then a bad client update could make your account unrecoverable, similarly to a mastodon server going bad.
The CEO is a musk toe-sucker whose been cheering on all of his shittiest ideas.
Jack is not the CEO, and he’s in minority on the board
deleted by creator
How exactly? In what ways do you think that influences bluesky development?
First of all, “enshittification” refers to monopolistic business practices, not… account portability or whatever you’re trying to say. It can’t be engineered away. Mastodon (the company) is nonprofit, BlueSky is for-profit. Furthermore, unlike Mastodon, there is no functional difference between BS servers, so the “freedom” to change is a moot point when bluesky (the company) controls everything.
Also the CEO cut her fintech teeth on cryptocurrency. Saying she’s not a fan of crypto is just plain wrong.
A lot of words for “I didn’t know you could use the network without using servers controlled by Bluesky”
The network is the thing that’s controlled by BS, a for-profit company who’s CEO is a crypto fan.
I’ve already explained how they have designed it so they can’t control it. Just use web-DID and your own domain handle on your own PDS, and then you can connect to a 3rd party relay (BGS, the CDN like cache) and whichever feeds and moderation tools and filter subscriptions you like. You don’t need to touch the official servers at all.
The network doesn’t use any cryptocurrency technology. There’s no blockchain, etc.
nobody said they did