logoalt Hacker News

pfrazeyesterday at 3:26 PM4 repliesview on HN

Yeah I’m the guy quoted in the opening of the article.

Yes. Be wary of Bluesky. That’s our whole point. Run the infrastructure on your own. Build separate companies.

Most of the complaints here are just about the cost of scale. You are able to fetch the whole network and its history, and that costs time and money. The only structural centralization is PLC, which is being factored into an independent org.


Replies

evbogueyesterday at 8:39 PM

I'd like to encourage anyone who is wary of Bluesky to check out Paul (and Dominic's) back-in-the-day project Secure-Scuttlebot which solved most of the issues that Bluesky suffers from by using content addressable storage and signing key cryptography correctly.

The actual SSB codebase has been kind of broken since 2020, but I have a fork on my own Github that works and comes with a basic client that you can vibe/claw on top of: https://github.com/evbogue/ssbc

I'm happy to supply pub invites to anyone who wants to play around with the old sbot with me as we work towards making social media distributed again.

show 1 reply
bjoliyesterday at 8:30 PM

Considering how hard it has been, and to some extent still is, to run your own Bluesky instance, the main problem is that it automatically becomes centralised in a way that no open protocol will solve.

If 97% of your users are on one instance it is not a distributed platform. Applying this to mastodon, I am pretty sure most people would consider it a problem if mastodon.social started getting more than 40% of active users (currently at about 15 iirc).

kevinakyesterday at 9:49 PM

Moving the PLC to an independent org doesn't make it decentralized.

show 1 reply