> This year, I'm betting less social media as being better and in the long-run a new protocol that learns from the mistakes.

Can you list protocol level mistakes made by ATProto?

▲

verdverm 7 hours ago | parent [-]

Permissioned data is probably the most fundamental, the part I looked most deeply into myself. People want privacy over blasting everything out to the internet for anyone to scrape. The public by default forced upon users is a bad choice. The purported benefits never materialized. Many of the atmo developers have this belief they can skip the network effects, grift the data and social graph for their own use.

Here's the User Intent proposal that is super easy to implement, yet they have been sitting on it since: https://github.com/bluesky-social/atproto/discussions/3617 This would have been at least a middle ground to permissioned data, as would have been personal private data (bsky prefs generalized).

After that money, which I see as less of a protocol thing. A protocol or platform has to enable the people to make way more money than itself, at least 10x. (1) Bluesky should have created subscriptions for their service, they wouldn't have needed the private equity had they. (2) Bluesky did more to block others making money than enable it. Graze was in talks with them to enable the creators using their feed system to make money, until Bluesky walked away. (3) Permissioned data would unlock monetization without blockchain.

Permissioned data is being worked on, but the commentary from Bluesky is not promising. (1) Nobody in ATProto has built a permission system (that I'm aware of) (2) Bluesky are proposing a very simplistic system. This will put burden on app developers and create opposition the credible exit philosophy.

Record history / editing. The former should be at the protocol level, the later on feature that is highly desired, possible today, but they resist with fervor.

Bluesky could have put way more funding into the ecosystem, especially in hindsight with the $100M they picked up just after peak. Now they are struggling and stepping on that ecosystem, re: replacing Graze instead of supporting and integrating them with their latest "ai" stunt.

Compare this to Hytale and what they are doing. Night and day.

The Bluesky team has also made several PR mistakes, upsetting their base, they are really tone deaf. Hope the waffles are tasty!

▲

verdverm 7 hours ago | parent | next [-]

The PLC comes up a lot, and I understand the criticism, but it is also good enough for now and on the right trajectory, though the pace could be better, hut like much of the Bluesky development it has molasses in winter vibes. Long-term, multiple identity authorities can exist. Something like Handshake would have been ideal, another great project doomed by poor leadership.

Supporting delete is a good decision in my opinion, and likely a legal requirement. I also like that ATProto stuck a balance between decentralized and user experience. Properly federated systems are unlikely to appeal to the masses, re: blockchain.

Two other well designed parts of ATProto are how the algos and moderation work. Modular, composable, and anyone can participate. This would change with a properly permissioned protocol (zanzibar + macaroons imo) and encourage smaller social instead of big social.

▲

pfraze 6 hours ago | parent | prev [-]

Dude, we have been blogging about the development of the private data spec all year and shared the proposal draft a week or two ago. Sorry we didn’t pick yours.

	▲	verdverm 6 hours ago \| parent [-]
		[dead]