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. nilesh+1n[view] [source] 2025-08-07 17:34:01
>>ezfe+vf
Not only is the bluesky network highly centralized right now, its UI is designed to perpetually lock users into the main bluesky server. Even if you use your own identity, when sharing the URLs to the posts via the UI, the URL defaults to bsky dot app domain, which will break if the author ever moves to a second server.
◧◩◪◨
4. OneDeu+yG[view] [source] 2025-08-07 18:52:53
>>nilesh+1n
That's not actually true.

1. If you switch PDS all links continue working.

2. If you change your handle (for did:plc, did:web can't do this because DNS) it used to break links but nowadays this isn't a problem because handle resolution respects historical handle naming (I think it works by post+handle age but I can't remember).

3. Also if you share posts using the did syntax instead of handle syntax (which bluesky seems to be slowly changing over to, at least profiles do this now), it's stable regardless of handle changes.

4. If you want to switch frontends, you can use an extension or app like at://wormhole to do so. UX for this should improve over time but that's a big "eventually".

5. Hopefully the at:// URI format catches on but that's a long ways away given that browsers make using custom URIs an absolute nightmare.

[go to top]