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?

  • jmbmkn@beehaw.org
    9·
    1 year ago

    They chose not to after researching options. Pretty sure they decides account portability was a key feature needed and AP doesn’'t do this. As in taking your account and all your posts and data witj you to a new server. I assume there is a technical reason why this would be very difficult to add to AP/Mastodon otherwise they could have just added it themselves.

    • Corgana@startrek.website
      2·
      1 year ago

      It’s nothing to do with that, they made the AT protocol because is structured in a way that ensures that bluesky (the company) will always control the network. They wouldn’t be able to keep control with ActivityPub, it’s the same reason Threads will never implement it.

      All the stuff about account portability is a distraction. Think about it: where would one move an account to anyway? Another BS node? Why? Unlike Mastodon instances there is no functional difference.

          • Natanael@slrpnk.net
            2·
            1 year ago

            This line is self contradicting

            So the storage layer is “neutral”, accounts are “portable”. That to me means that node operators will have no agency in the system. Discoverability/search/recommendations are done in a separate layer, and the way the system seems to be designed (nodes have no say, they just provide the data) effectively places all the power with these “reach” algorithms.

            3rd party feeds and recommendations and discovery already exists. They are also not dependent on the continued existence or openness of the bluesky servers. You can control your own experience and it’s easy to find and switch between feeds. Having more subscribers to your feed doesn’t make you more powerful in the context of network effects. If people stop looking your feed they’ll dump it.

            Also, node operators have full control of what they forward to clients. They can absolutely apply moderation filters, and this is one of the expected means for such nodes to market themselves to their communities - “we have default feeds and moderation which suits your community”.

            So it’s a winner-takes-all system that strongly avantages whoever starts building their dataset early and can throw as much money at it as possible.

            Nonsense, the network uses relay servers which acts as open CDN servers and the firehose feed is open AND 3rd party hosted feed builders already exists (and they’re open source so you can copy them), you don’t need to waste duplicate work on building datasets. This network is cooperative. It has absolutely no winner-takes-all effects, it explicitly encourages division of labor and mix-and-matching multiple 3rd party services.

            Another pretty good sign that BS’s decentralization is actually b.s. is the fact that the Decentralized Identifiers (DIDs) used by BlueSky are currently “temporarily” not actually decentralized. The protocol uses something imaginatively called “DID Placeholder”. If I were a betting man I would bet that in five years it will keep on using the centralized DID Placeholder, and that that will be a root cause of a lot of shenanigans.

            Then use web-DID which already is fully decentralized

            Jack is not involved with bluesky anymore, he’s in nostr land now. He doesn’t have majority on the board and isn’t influencing development.

            There is no way to opt-out from “reach” algorithms indexing one’s posts, as far as I can see in the ATproto and BS documentation. So fash/harassers would be able to choose an algorithm that basically recommends targets to them.

            Moderation tools like this is in the works, it’s not complete yet. Mute/block filters already exists, and label services for moderation are being worked on

            A whole lot of directly false nonsense and irrelevant arguments and ignorance of what the devs are working on