zlacker

[return to "Building Bluesky comments for my blog"]
1. philip+ke[view] [source] 2025-08-07 17:03:37
>>g0xA52+(OP)
I'm not optimistic about BlueSky's profitability - the current free-at-point of use is a result of VC funding.

So personally I'd be wary of adopting it. I think it's likely the API gets locked down and the comments break in a couple of years.

◧◩
2. danabr+O01[view] [source] 2025-08-07 20:40:34
>>philip+ke
Note Bluesky is architected to be downstream of PDS (personal data servers) which any user can switch to another provider, and the Bluesky app server acts as an aggregator (but anyone else can build their own aggregators — and people already have). So as Natalie notes in the post, you don’t even “have to” use the Bluesky app API to access the posts. You can get them from a third-party app server (“app view”) or even have your own. They’re all aggregating from the same data source.
◧◩◪
3. fsflov+Oe2[view] [source] 2025-08-08 08:23:43
>>danabr+O01
https://pluralistic.net/2024/11/02/ulysses-pact/#tie-yoursel...

https://dustycloud.org/blog/how-decentralized-is-bluesky/

◧◩◪◨
4. danabr+jA2[view] [source] 2025-08-08 12:14:22
>>fsflov+Oe2
Some of this is already outdated. With the switch to non-indexing relays (“Sync 1.1”), people are already running independent relays quite cheaply. There are also actual independent AppViews coming up.

https://whtwnd.com/bnewbold.net/3lo7a2a4qxg2l

◧◩◪◨⬒
5. fsflov+H95[view] [source] 2025-08-09 12:27:15
>>danabr+jA2
I'll believe it when I see a list of relatively large, independent servers, which don't go offline all together in case of network problems.
[go to top]