Elektrine lite

← Feed

@ricci@discuss.systems

2026-06-22 03:40 UTC

@dialecticalmusings @cwebber@social.coop @innocentzero@social.tchncs.de > I was under the impression that a PDS can directly communicate with another PDS without the need of an intermediary relay or AppView. Isn’t that correct? This is not correct from the "pure" atproto viewpoint. A PDS is simply a store of records, it has no user interface, it has only an API that users use to create and maintain their records (posts, etc.) and a streaming API for others to get copies of those records. The only visible interaction that users have with their PDS is the oauth login flow. Think of it like an s3 bucket, if that is meaningful to you. In this context, it makes no sense for PDSes to talk to each other. Wafrn looks much more like the "instance" that the author of this article calls nonsensical in the atproto world, because it combines several things, including the store of many users' data including users who are not "local", the web interface and/or APIs that users access it with, and more. Wafrn does work in this world, but it is very much in opposition to the architecture the article at the root of this thread is claiming as the "correct" use and understanding of atproto.

Replies (1)

  • @innocentzero@social.tchncs.de @ricci@discuss.systems [Removed [at]cwebber, based on what you said elsewhere] Yeah, my impression was incorrect. Looks like the Bluesky Jetstream is part of the picture, I think wafrn uses it to filter (using DID) only those posts/hashtags followed by its users.

    Open ##5120020