News for hackers. Stuff that matters.
Re:NFL teams can't use Bluesky by PaulHoule on Wednesday January 22, 2025 @02:05PM (#42796316)
So if I am a bsky.social user the content gets stored in their database, and if I have a PDS the content gets stored in my PDS?
Re:NFL teams can't use Bluesky by pfraze on Wednesday January 22, 2025 @02:26PM (#42796522)
Yep. If you look at the repo browser for @bnewbold.net, you can see his blogposts: https://atproto-browser.vercel.app/at/did:plc:44ybard66vv44z...
Re:NFL teams can't use Bluesky by verdverm on Wednesday January 22, 2025 @02:30PM (#42796562)
Some more interesting breadcrumbs (what does it take to implement a repo)

https://github.com/bluesky-social/atproto/discussions/2644

Re:NFL teams can't use Bluesky by verdverm on Wednesday January 22, 2025 @02:26PM (#42796524)
My understanding is that your content gets stored in your database, regardless of PDS host. Bluesky hosts most PDS

I believe each user gets a dedicated sqlite database, or at least a dedicated repo. I recall reading somewhere about the implementation moving to use sqlite

Re:NFL teams can't use Bluesky by PaulHoule on Wednesday January 22, 2025 @02:45PM (#42796726)
"My" instance of sqlite that they host?
Re:NFL teams can't use Bluesky by verdverm on Wednesday January 22, 2025 @02:54PM (#42796812)
yeah, that is my understanding, if I understand your question correctly.

Of course it is all hidden from view, there is a merkle tree involved, and you probably want to use a higher level client than SQL

This talks about why SQLite and not Postgres

https://github.com/bluesky-social/atproto/discussions/2287

Repository spec:

https://atproto.com/specs/repository

Small program to export:

https://github.com/bluesky-social/cookbook/tree/main/go-repo...