Journey to a distributed PDS: OAuth and deeper thoughts on why this experiment exists...

It's been a while since my last update, or even any progress, on the distributed PDS. I started looking into it again last week though and have hit quite the show stopper... OAuth 🫠

I'm not going to pretend like I fully understand the specs of how OAuth works, but I know enough I think. With OAuth, the client and server use something called DPoP. As part of this process, the server will…

Read more →
Bluesky PDS with Podman on CentOS Stream 10

This is based on the following documentation from the official Bluesky GitHub:

We'll keep SELinux in enforcing mode and install a policy module to allow the PDS to work. CentOS Stream is not an officially supported distribution by the upstream PDS maintainers -- this is my own working setup -- so please do not bother them with support questions for a CentOS Stream host. In lieu of that, you're…

Read more →
The journey to a distributed PDS

Hopefully this is part 1 of many posts, describing my progress into running a PDS across many nodes or devices.

A few weeks ago someone said something about running a PDS in a browser that got me thinking... What if a PDS was hosted on a device. Your phone, tablet, laptop etc as part of an app. It would allow anyone to host their own PDS without the infrastructure barrier that technical minded…

Read more →
A varied ecosystem and terminology.

As soon as you have an open protocol you will have an ecosystem building up around it, and soon as you have an ecosystem you have people doing stuff differently. This is especially true when dealing with an open protocol built on a set of distributed pieces working together to create a whole.

atproto is such a protocol, system and ecosystem and it has a problem ... well it has many problems…

Read more →
Page 1