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?

    • Natanael@slrpnk.net
      0·
      9 months ago

      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.

      • Michał "rysiek" Woźniak · 🇺🇦@mstdn.social
        0·
        9 months ago

        @Natanael you seem to continue to focus on PDSes even though I explicitly said it doesn’t matter which PDS you’re on, the secondary centralization (and thus control) happens in the “reach” layer, outside of what PDSes do in ATproto.

        In other words, changing a PDS gives you way, way less agency in BS, compared to agency you get with changing an instance on Fedi.

        BS is designed to make that secondary centralization happen, and to be where the real power in the system is.