• lone_faerie@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      20
      arrow-down
      1
      ·
      2 days ago

      It’s 100% centralized, but with the ability to be decentralized. Sorta like Threads before they started federating

      • sem@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        2
        ·
        2 days ago

        The “ability” to decentralize has costs that scale quadratically. So in every practical sense, it cannot be decentralized. At best it could have a few servers that participate.

        • Natanael@infosec.pub
          link
          fedilink
          English
          arrow-up
          3
          ·
          2 days ago

          No, it doesn’t scale “quadratically”. That’s what going viral on Mastodon does to a small instance, not on bluesky. Pretty much everything scales linearly. The difference is certain components handle a larger fraction of the work (appview and relay).

          Both a bluesky appview and a Mastodon instance scales by the size of the userbase which it interacts with. Mastodon likes to imagine that the userbase will always be consistent, but it isn’t. Anything viewed by a large part of the whole Mastodon network forces the host to serve the entirety of the network and all its interactions. So does a bluesky appview, in just the same way, but they acknowledge this upfront.

          Meanwhile, you CAN host a bluesky PDS account host and have your traffic scale only by the rate of your users’ activity + number of relays you push these updates to. Going viral doesn’t kill your bandwidth.

            • Natanael@infosec.pub
              link
              fedilink
              English
              arrow-up
              1
              ·
              edit-2
              23 hours ago

              In fact, it is worse than the storage requirements, because the message delivery requirements become quadratic at the scale of full decentralization: to send a message to one user is to send a message to all. Rather than writing one letter, a copy of that letter must be made and delivered to every person on earth

              That’s written assuming the edge case of EVERYBODY running a full relay and appview, and that’s not per-node scaling cost but global scaling cost.

              Because they don’t scale like that, global cost is geometric instead (for every full relay and appview, there’s one full copy with linear scaling to network activity), and each server only handles the cost for serving their own users’ activity (plus firehose/jetstream subscription & filtering for those who need it)

              For Mastodon instance costs, try ask the former maintainers of https://botsin.space/

    • Victor@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      3 days ago

      This is a little bit more black and white compared with the other responses. 🙈