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.
Important note here, Eurosky and Bluesky aren’t two separate instances where your data is separate from Bluesky. When you use EuroSky, you’re just using BlueSky and it has all the same access to your data. The difference is just that your data is stored on EuroSky’s servers.
ATproto doesn’t have instances the way Mastodon or Lemmy do with Activitypub, and privacy is not really something it does.
Good to know!
Mastodon users can also federate with Bluesky through Bridgy Fed, but it’s opt-in on both ends. This Eurosky “mu” thing sounds like a better way to interact with Bluesky if that’s what you want to do, but it doesn’t federate with the Fediverse.
Mu is just a bluesky client. Eurosky is a PDS, the part that store user data in AT Proto ecosystem. The part that aggregates user data into a bluesky feed, the AppView, is still run by bluesky. Eurosky is planning on running one but it’s not done yet. But I would argue that this is less critical than the user data storage part.
AT Proto does not work like ActivityPub.
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.
So, if tomorrow bluesky vanished, my data would be safe on Eurosky, but no one could interact with it?
The way ATproto works is all your data is stored in a database called a PDS, every post, reply etc. unlike Mastodon or Lemmy, this PDS isn’t a part of an “instance” like Lemmy.world, and it doesn’t actually matter who hosts it. You could host the PDS yourself.
BlueSky is not an instance, it’s an “AppView” which is just a predefined set of rules/API, and it expects certain data in your PDS to look a certain way, and then to simplify a bit it just pulls the data out of your PDS and everyone else’s PDS all over the internet. The thing OP linked to is a Client that connects to the BlueSky AppView. But all the data still just lives in whatever PDS you store your data in. So if BlueSky disappeared tomorrow, you could write another AppView that just has to fit the same schema that the data in your PDS uses and it’d be like it never left.
To simplify further, if Mastodon and Lemmy work like Email, ATproto words like RSS. Your PDS is like your own hosted blog. Bluesky is like an RSS reader that just reads everyone’s PDS data. If the RSS reader vanishes, your data is still there, you just have to make a new RSS reader to read the data
To simplify further, if Mastodon and Lemmy work like Email, ATproto words like RSS. Your PDS is like your own hosted blog. Bluesky is like an RSS reader that just reads everyone’s PDS data. If the RSS reader vanishes, your data is still there, you just have to make a new RSS reader to read the data
Thanks for coming down to my level, appreciate it :)
Oh yeah it’s not just you, ATproto is very different from our usual way of thinking. Took me a bit to wrap my head around it at first too
On the AT Proto there a different kinds of data, identified by what’s called a lexicon. Bluesky’s aggregates data with a lexicon matching
app.bsky.*(likeapp.bsky.post,app.bsky.like…). If Bluesky goes down you can still interact with your data, not just through the main Bluesky AppView. There are other apps that have their own lexicon (Sifa ID, a LinkedIn like, Tangled, a code forge, Stream.place, a Twitch like, Leaflet for blogging…). And even for Bluesky lexicon, there are other AppViews that aggregates the Bluesky lexicon (I think for now only Blacksky have one, Northsky and Eurosky are planning one but that’s not done yet).
Eurosky is just bluesky, bridgy fed works all the same.
It’s not “just bluesky”.
It’s only a PDS, the AppView is still
EuroskyBluesky.What OP linked to is actually EuroSky’s new AppView, but you’re correct that none of this data is somehow separated from the BlueSky users.
EDIT: Oh Woops it’s actually not an AppView yet
