CIRCLE WITH A DOT

@heliomass the part "your data can be owned by you, a third party or the service you use and that allow any other service to use this data without asking the service you use" is indeed weird at first. But I wouldn't say it's any more complicated than activitypub, which needs to explain "instances" to people. You say you're on mastodon but youre really on cosocial which uses mastodon, but you download a mastodon app to use cosocial.ca. It's not easy to explain to non-techy people either.

@heliomass There are some of them for the bsky lexicons (the microblogging on atproto) like blacksky.community, deer.social, surf.social (also AP-compatible) and gander.social (closed beta for now).

But atproto was never designed to be decentralized the way that mastodon/activitypub is. The main decentralization point is at the PDS level, where the "instance" (like bsky.social) doesn’t own said data and if they do things you don’t like, then you start using something else without that implying a migration (just start using blacksky.community). If your PDS is at the same place as your instance (as for most people), then that implies a migration (but it won’t change your identity the way that it does for mastodon).

On the governance front, a working group at the IETF was created to standardize the core parts of atproto: https://atproto.com/blog/kicking-off-the-atp-working-group

@heliomass strange take, bsky PBC has done basically everything they needed so far to make atproto "bsky PBC-proof". What makes you think otherwise?

Remember when SSDs came out and Windows booted fast? I miss this