An atproto PDS whose only durable storage is an object store. Any node serves any request, one node can run a personal server for free, and a few nodes can carry all of Bluesky's write load.
vlpds/README.md at main · jazware/vlpds
Very Large PDS, a world-scale, incredibly efficient, incredibly resilient, atproto personal data server - jazware/vlpds
PDS operator guide — atproto-crates
Operating atproto-pds: production status, endpoint surface, storage profiles, build flags, the full environment variable reference, and the deployment modes that are deliberately not wired up.
Adversarial ATProto PDS Migration | Blog
An ATProto account lives on a Personal Data Server (PDS), and that service needs to be hosted somewhere by someone. There are a lot of options here, like a Raspberry Pi in your closet, a rented VPS in a datacentre, or a batteries-included service like bsky.social.
com.atproto.repo.listRecords | Bluesky
*This endpoint is part of the atproto PDS repository management APIs. Requests usually require authentication (unlike the `com.atproto.sync.*` endpoints), and are made directly to the user's own PDS instance.*
PDS Directory | ATProto PDS Index
Complete directory of Personal Data Servers in the Atmosphere.
crate.social — publish structured records to your ATProto PDS
Crate is a custom-lexicon publishing service for ATProto. Define your record types, import from anywhere, query from everywhere.
Embracing ATProto, part 1: Setting up a PDS
In this series of posts, I'll explore my journey into setting up my workflows and services for atproto. The first step is setting up my PDS. Let's start with a bit of explanation for all this lingo.
com.atproto.repo.createRecord | Bluesky
*This endpoint is part of the atproto PDS repository management APIs. Requests usually require authentication (unlike the `com.atproto.sync.*` endpoints), and are made directly to the user's own PDS instance.*
haileyok/cocoon
An ATProtocol PDS (Personal Data Server) written in Go with a SQLite block and blob store
Why atproto has not been explored by game devs? Saves, collectibles and inventories can all be stored on a PDS Imagine carrying on your character from one game to another or between the same series instalments Storing stuff like CS2 skins on atproto should be a no brainer How cool is that?
Hi protocol friends! I've been cooking up a Very Large PDS (vlpds) implementation capable of scaling up to billions of accounts and down to just one. It uses Object Storage as its only state, supports HA operation, live scaling up and down, is feature-complete with the reference PDS, and is FOSS.
Overview · vlpds docs
vlpds.jazco.devthe single most important part of atproto is the PDS as a user-controlled auth and storage layer to which clients can connect directly. death to appviews
Authenticated Transfer Enables Orchestration - nekomimi
blog.nekomimi.petI recently got super into the ATProto spec and how different services use PDS to store the data, I put together a quick client-only website that presents all those records in a single, consolidated feed of all my activity: at.diego.codes
at.diego.codes — Diego Vicente
at.diego.codes
