For one thing the “AppView” as I believe it’s called. When I looked at the whole system a month or two ago the documentation wasn’t great at giving a clear high-level overview and the details are hazy in my memory. It’s at least as hard to figure out as the constellation of protocols used in conjuction with ActivityPub. Among other potential problems the protocol layer that would allow it to be fully decentralized is just missing. If it was there, I think it might look something like ActivityPub added on top of what already exists.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Which parts of the protocol’s design are mostly centralized?
For one thing the “AppView” as I believe it’s called. When I looked at the whole system a month or two ago the documentation wasn’t great at giving a clear high-level overview and the details are hazy in my memory. It’s at least as hard to figure out as the constellation of protocols used in conjuction with ActivityPub. Among other potential problems the protocol layer that would allow it to be fully decentralized is just missing. If it was there, I think it might look something like ActivityPub added on top of what already exists.
From my browser history here’s one attempt to sum it up: https://dustycloud.org/blog/how-decentralized-is-bluesky/
Design isn’t centralised but the implementation and tooling currently are
https://alice.bsky.sh/post/3laega7icmi2q