Finally time to drop the thing I've been working on for weeks: Bluesky without Bluesky – I ran a full stack PDS/Relay/AppServer/Client stack using no bluesky code!

Finally time to drop the thing I've been working on for weeks: Bluesky without Bluesky – I ran a full stack PDS/Relay/AppServer/Client stack using no bluesky code!

running your own relay and such is in theory good but how you do you keep track of all the pds out there without going back to the Bluesky relay or someone's project that generates a list on a GitHub repo

So here's why we experienced a problem with Eurosky last night 🧵 Our systems (the PDS) were up and running as normal. The issue was that data from our systems stopped flowing into the part of the network (the relay) that lead to the Bluesky app.

So every now and then I will try to post my way into closing that gap and clarifying that neither Bluesky nor the Discover feed define this network. And you shouldn’t need to be an embedded systems engineer to get what you want out of these networks of apps.

Am I missing something or is the Bluesky new-PDS daily relay limit for an _entire PDS_ lower than the limits they give to a _one single repo_ on their hosted PDSses? docs.bsky.app/docs/advanced-guides/rate-lim…