Post
its live at https://atproto.africa/
theres 5 ppl/orgs running publicly accessible relays, you can compare them at https://compare.hose.cam/
i know of at least another 5 ppl who run their own relays but dont publicly advertise the endpoints
atproto splits this into 3 separate parts
data hosting is on a PDS (personal data server), and you can any PDS you want to use the bluesky app
a separate piece of software called an appview indexes the entire network, and counts the likes on all posts
the client is separate again, this is just a framework that gets its data from the appview
bluesky the company provides all 3 parts, but you can create your own individual part for each layer and still use the same network
i'm still quite confused between the actual differences between atproto and activitypub.
could you put it down in a diagram or something?
That's a Relay. The AppView is the client. Otherwise your description is pretty much right;
https://dustycloud.org/blog/how-decentralized-is-bluesky/
TBH I'm not sure about this, but I'm guessing all 3 component play a role in counting Likes. With Likes indexed by the Relay, stored in the PDS of the account that made the post, and displayed by the AppView.
no, when i use index i mean creating a database of the entire network. the relay just broadcasts the network
the relay is just an optimisation piece that prevents an overload of consumers on PDSes, that has gotten wayyyy to much attention compared to how important it is
appviews is definitely not a client? its a database with all interactions. constellation is a minimal example of an appview: https://constellation.microcosm.blue/
@laurenshof
> the relay is just an optimisation piece that prevents an overload of consumers on PDSes
Unless @cwebber is wrong (and she hasn't been corrected yet), the Relay sits between the PDS and the AppView. It's not possible to overstate the power that gives the operators of the only Relay in the current network.
> appviews is definitely not a client? its a database with all interactions
These are not mutually exclusive.
thats how blacksky works:
they first created their own data storage for blacksky users. people who are on the blacksky PDS can use any client or app as the same, so they also could use the bluesky app and exactly nothing changed
blacksky then released their own client at https://blacksky.community/. literally any atproto account (including nonblacksky users) can use this. when you use this client you see the exact same network as if you used bsky.app
Thank you @laurenshof for all this info! Really helpful
so it's a bit like matrix but the synapse server is split into "thing with all the messages" and "thing that makes messages work on other things with all the messages"
OK, so are they running their own Relay? I know they aspire to, but I had a good rummage around the web and couldn't find clear confirmation this has happened.
Until there is more than one Relay, the ATmosphere is only as decentralised as early Titter, back when API access was freely available for third-party apps. In others words, it's not.
>are they running their own Relay?
i believe the answer is a resounding "fuck yes"
"This library is a work in progress. Things will change. Things are incomplete. Things will break. Until the project reaches version 1.0.0, stability will not be guaranteed."
https://github.com/blacksky-algorithms/rsky
But are they running a Relay in the wild, and could I use it in place of the BS Relay? Nothing in this repo answers this question.
its live at https://atproto.africa/
theres 5 ppl/orgs running publicly accessible relays, you can compare them at https://compare.hose.cam/
i know of at least another 5 ppl who run their own relays but dont publicly advertise the endpoints
totally agreed on blacksky's independent implementation being very impressive!
I do not think relays are that important though:
- phil runs 3 independent relays with microcosm, and they have the "problem" that nobody is actually interested in consuming from an independent relay
- phil's relay comparison (https://compare.hose.cam/) gives an indication that were close to realtime comparisons between relays to spot misbehavior of relays
like, on paper relays look like a bottleneck in the system architecture, but a system that you can drop-in replace with alternatives or self-host for like 30$/month, while being straightforward to spot bad behaviour is not an actual bottleneck imo
(tbc, this is partially based on phil showing their upgraded unreleased version of the relay compare, where they easily managed to find the 4 pds hosts that bsky has banned from their relay (obvious nazi pdses))
A space for Bonfire maintainers and contributors to communicate
