←back to thread

420 points rvz | 3 comments | | HN request time: 0s | source
Show context
verdverm ◴[] No.41412716[source]
I left Xitter about 6 weeks ago and went all in on Bluesky. Took time to give feedback to the algo, but it's doing much better these days. I don't feel like I'm missing out on much, you'll get the same news & events on Bluesky. A lot of people who were scared of losing their following are reporting more, better engagement with lower follower counts.

What I really like about it is the ATProto, which while imperfect, seems like the best current design for the next gen of social media built on a federated foundation.

- DID for identity

- PDS for data mobility

- algo feed & moderation choice, you can build your own and anyone on Bluesky can use it (https://bsky.social/about/blog/03-12-2024-stackable-moderati...) If you didn't see, they recently added anti-toxicity features and are looking towards community notes

- Bluesky is the twitter like view, but you can build anything on ATProto and leverage the shared infra

I'm personally working on a "reddit" like view of the Bluesky network. Not a reddit clone, but a different way to organize the same information around topics, news events, and/or links. One could also design their own Lexicon and build something very close to reddit. One of the cool things is that all the objects for all apps are stored into a single SQLite database per user. So if you want to move your data to a different host, all of the apps, content, and connections survive that migration.

replies(7): >>41413110 #>>41413357 #>>41414610 #>>41415196 #>>41417624 #>>41418319 #>>41418341 #
declan_roberts ◴[] No.41413110[source]
Blueskey seems to have all of these neat features that developers/nerds seem to like, but literally nobody else cares about.
replies(8): >>41413147 #>>41413359 #>>41413547 #>>41417695 #>>41418051 #>>41418073 #>>41418119 #>>41418172 #
throwaway48476 ◴[] No.41413547[source]
A proper decentralized publishing platform would be content addressed not federated which retains all the downsides of centralization.
replies(1): >>41413616 #
pfraze ◴[] No.41413616[source]
The bluesky team worked previously on IPFS and Dat/Hypercore and Secure Scuttlebutt. Whyrusleeping - one of the core authors of IPFS - has been an active technical advisor from the start. ATProto is basically those p2p & content addressed techs moved into the server stack. None of us are bullish on client side p2p for large scale publishing or social applications, and we spent 10 years each doing that.
replies(3): >>41413668 #>>41413669 #>>41419170 #
1. throwaway48476 ◴[] No.41413668[source]
P2P is hard, but that does not mean undesirable.
replies(2): >>41413712 #>>41415439 #
2. pfraze ◴[] No.41413712[source]
Feel free to pick up where we left off, but just know that you're in for a lot of pain on key sync, device pairing, unreliable data availability, poor connection establishment latency, high end-user device resource usage, and very small data indexes which make it nearly impossible to produce even moderately-sized social networks.
3. kelnos ◴[] No.41415439[source]
I think you're looking at it the wrong way. It's not just hard, but the user experience with it is just terrible. The masses will not use it. If the masses will not use something that requires network effects to be successful, there's no point. These problems may be solvable, but I think I'd trust the opinions of people who have worked on it for years and decided to do something else.