zlacker

[return to "Building Bluesky comments for my blog"]
1. oelleg+Ne[view] [source] 2025-08-07 17:05:36
>>g0xA52+(OP)
I love the approach but I’d go with Mastodon which is an actual open protocol with multiple servers and clients and clearly not for profit
◧◩
2. ezfe+vf[view] [source] 2025-08-07 17:07:34
>>oelleg+Ne
To be clear, so is blue sky – you can run a Bluesky server yourself just like mastodon
◧◩◪
3. dewey+ei[view] [source] 2025-08-07 17:16:48
>>ezfe+vf
Do you know anyone who does? There's many big and open Mastodon instances but I've yet to see a Bluesky one.
◧◩◪◨
4. OneDeu+9H[view] [source] 2025-08-07 18:56:12
>>dewey+ei
You normally don't notice tbh. Switching PDS is entirely invisible to the frontend. There's a lot of self hosted PDS users (since it's basically a small go router + sqlite) but there's also bigger community PDS projects being spun up including blacksky and northsky.

As for frontends, there's a bunch of them and a lot of them focus on changing the UX. But for self hosted "bluesky", there is https://deer.social which is a forked client that still relies on the bluesky appview/backend and there is https://zeppelin.social which is downstream of deer social but also runs their own appview independent of "big bluesky".

◧◩◪◨⬒
5. dewey+hI[view] [source] 2025-08-07 19:02:11
>>OneDeu+9H
Thanks for the explanation, I was almost certain I'm missing something.
[go to top]