70
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Aug 2026
70 points (93.8% liked)
You Should Know
47078 readers
157 users here now
YSK - for all the things that can make your life easier!
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must begin with YSK.
All posts must begin with YSK. If you're a Mastodon user, then include YSK after @youshouldknow. This is a community to share tips and tricks that will help you improve your life.
Rule 2- Your post body text must include the reason WHY YSK:
In your post's text body, you must include the reason "Why" YSK: It’s helpful for readability, and informs readers about the importance of the content.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Posts and comments which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding non-YSK posts.
Provided it is about the community itself, you may post non-YSK posts using the [META] tag on your post title.
Rule 7- You can't harass or disturb other members.
If you harass or discriminate against any individual member, you will be removed.
If you are a member, sympathizer or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people and you were provably vocal about your hate, then you will be banned on sight.
For further explanation, clarification and feedback about this rule, you may follow this link.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- The majority of bots aren't allowed to participate here.
Unless included in our Whitelist for Bots, your bot will not be allowed to participate in this community. To have your bot whitelisted, please contact the moderators for a short review.
Rule 11- Posts must actually be true:
Disinformation, trolling, and being misleading will not be tolerated. Repeated or egregious attempts will earn you a ban. This also applies to filing reports: If you continually file false reports YOU WILL BE BANNED! We can see who reports what, and shenanigans will not be tolerated. We are not here to ban people who said something you don't like.
Rule 12- Linking directly to a video as a source is not acceptable.
Video only posts are responsible for an outsized portion of rules violations. Your post must contain text and meet the requirements of the previous rules.
Rule 13- If you file a report, include what specific rule is being violated and how.
Partnered Communities:
You can view our partnered communities list by following this link. To partner with our community and be included, you are free to message the moderators or comment on a pinned post.
Community Moderation
For inquiry on becoming a moderator of this community, you may comment on the pinned post of the time, or simply shoot a message to the current moderators.
Credits
Our icon(masterpiece) was made by @clen15!
founded 3 years ago
MODERATORS
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.
https://overreacted.io/there-are-no-instances-in-atproto/
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
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
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).