Personal Data Server
component of BlueSky architecture
reference code https://github.com/bluesky-social/pds is shell scripts to pull code which is TypeScript and Go
Setting up a PDS is pretty simplistic in comparison. It’s just going to host posts in a database. There’s no flashy timeline, no custom css or other pieces of flair to show off. It’s just a place to store data and be freed from a large corporation controlling that content.... Being able to control your own content, move it from one PDS to another, and still retain your core identity may be boring but it’s the missing piece in the fediverse right now. Sure, you can move your followers. But not your posts nor your identity (your username changes every time you switch instances). And your posts are important. I want to get a better understanding of how that works.
The db is Sqlite
- https://github.com/bluesky-social/atproto/tree/main/packages/pds/src/actor-store/db/schema
- I think it's pretty schemaless, using "Lexicons" as type-templates (like a taxonomy?)
Edited: | Tweet this! | Search Twitter for discussion