Doesn’t help that they have offered no explanation at all.
Doesn’t help that they have offered no explanation at all.
Discoverablility of what?
How would this help? What is the problem this addresses?
Many of the functions provided by a Mastodon service is split into separate services in the AT Protocol. This means there are instances that just handle an end users data, instances that just handle indexing and streaming out the amalgamated end user data being streamed to the “relay”, there are instances that are just filtering the stream from the indexing relay. so basically the various backend parts are modular with the AT Protocol rather than monolithic as is assumed by the ActivityPub protocol where separation is assumed to be only between the frontend and backend of the service.
Bluesky has no documentation for running a relay (indexing node). It doesn’t seem like they intend to have any documentation on it any time soon. But it is possible to set one up yourself. I don’t know anyone that has done so.
Peering agreements have been around for a long time on the internet, they’re part the backbone of the internet.
Peering agreements for internet traffic, what a stupid concept.