In my opinion, that is a worthy YSK because people don’t know that they can view and interact with Bluesky content without giving your data to an American for-profit entity.
In my opinion, that is a worthy YSK because people don’t know that they can view and interact with Bluesky content without giving your data to an American for-profit entity.
Illuminating read. Thanks.
It doesn’t answer the obvious question though. The host (Bluesky/Eurosky, which apparently is called a PDS) is still effectively an instance, isn’t it? You can host your own, but you’d probably use one that’s already set up. It doesn’t seem that different from Mastodon in that sense.
The other big question is, how does the migration work? I’ve heard that Mastodon’s migration is less than perfect. But this blogger says they’ve moved from bsky to Eurosky, and I just want to know how that works – if I have a client subscribed to that account back when it was on bsky, how will my client know where to look now?
Edit: okay, I did a little searching, then after getting no useful results gave up and asked the big data machine that’s making everyone’s lives worse. I kinda get it now, but not enough to explain here. But it sounds like a good system.
I still wouldn’t call it an instance, that’s only data storage.
For migration it’s quite easy, there are different tools for it, Eurosky have one , PDS Moover is another, there are probably others.
As for finding people data over different PDS, an account is actually identified by a unique id, a DID. And there is another brick, another server, the PLC that store on which PDS is a DID stored.
So the PCD is centralized, is it not?
For now there is only one PLC, in a independent organisation. But it’s not really an issue and there will probably be others in the future, but it’s low priority.
https://docs.bsky.app/blog/plc-directory-org