Atproto Ethos - AT Protocol
atproto.com
A deep dive into the philosophical and aesthetic principles underlying the design of AT Protocol.
      • Ulrich@feddit.orgEnglish
        11·
        18 hours ago

        Because it’s not functional without BSky servers and BSky also retains control of moderation.

        • Little8Lost@lemmy.worldEnglish
          11·
          11 hours ago

          After reading the article i think you might be wrong with this one.

          From what i got now is that there are 3 layers

          First is storage which can be completly or is decentralised

          Then backend/server/application layer which can be bsky or whatever ticktok alternative gets made which is not decentralised

          and then user layer/view which depends on the application

          What i want to say is that the relay can be exchanged through something else and then entirely including moderation and all

          So pro atProto is:

          • data seems to be actually decentralised
          • applications sharing the data
          • everyone gets the data

          And pro ActivityPub is:

          • more alternatives of the same application/server
          • way better control over data (federation & defederation)
          • servers interact with each other nativly (atPr seems to let the servers only interact with data)
          • more efficient (servers can update clients, in case of at least bsky clients have to ask servers)

          pro ActivityPub? (unsure about the technical details)

          • moderation? As in shared lists
          • able to host by individuals? As in i dont need an compute intensive relay
          • flamingos-cant@feddit.ukEnglish
            2·
            4 hours ago

            But what about the DIDs, the things used to actually identify accounts within the ATproto ecosystem:

            But Bluesky has developed its own DID method, did:plc. Today, did:plc stands for “Public Ledger of Credentials”, however it originally stood for “Placeholder DIDs”, with the hope of replacing them with something else later. The way that did:plc works is that Bluesky hosts a web service from which one can register, retrieve, and rotate keys (and other associated DID document information). However, this ledger is centrally controlled by Bluesky.

            It’s literally not possible to have a functional PDS without registering with a Bluesky server and they maintain indefinite control over the ledger. All your data is tied to this DID, it’s how the entire protocol is designed to identify stuff, how decentralised is your data if it’s dependent on Blusky (the company) assigning you an identity?

        • Sl00k@programming.devOPEnglish
          24·
          17 hours ago

          This is just wrong. Another platform similar to tiktok(spark) is in beta with their own infrastructure outside of all Bluesky servers and they have to deal with their own moderation. They can choose to read in any Bluesky data they please and bluesky can do the same with theirs.

          If Bluesky shuts down all servers tomorrow they still exist. The federation is simply adopting their Lexicon into your relay and appview.

          If you want a microblogging platform specifically you can easily run your own infrastructure similar to running an instance, intake all BlueSky posts and if Bluesky shuts down your app will continue operating using BlueSkys lexicon, however you’ll have to manage your own moderation.