Plans for an atrium PDS?

[erlend-sh]

Now that Bluesky is becoming properly federated

• Migrating bsky.social to Multiple PDS Instances (Nov 2023) bluesky-social/atproto#1832

..are you planning to set up an atrium-based PDS? If so, consider my hand raised as a volunteer for testing ✋

My main interest is the intersection of ATproto and ActivityPub. There’s one Rust project in particular that is exploring this space in an interesting way:

• Full restructure kitsune-soc/kitsune#418
• ATproto / Bluesky interop kitsune-soc/kitsune#366

[sugyan]

As mentioned in #19, atrium-based PDS sounds interesting and is an issue I would like to try, but now nothing has been done yet. I think it will probably take a very long time to proceed with it as my hobby project because I don't have enough time to spare...

[str4d]

Relevant summary of what a PDS implementation needs to do: bluesky-social/atproto#2350

[DrewMcArthur]

i'm curious about implementing a PDS in rust - from what i can tell, your client library is constructed by parsing the atproto lexicon and generating code that makes http calls with the correct bodies. so com.atproto.server.create_account(...) is just a generated wrapper for GET /xrpc/com.atproto.server.create_account ... etc.

implementing a server would be more involved, since you'd have to implement each method (e.g. adding a new user to a DB), and then generate code to wire the xrpc/http calls from NSID to an actual method? would a library like tarpc make sense to use, or something like that? or am i totally off base? any thoughts to steer me in vaguely the right direction?

[erlend-sh]

@rudyfraser has been working on a rusty PDS here: https://github.com/blacksky-algorithms/rsky/tree/pds