Vision of a New World – Design Issues (2024)

ATProto team is familiar with SOLID, and we have a lot of respect for the people involved, but it didn't seem like it captured the right model for us. In particular, we felt it was important to debind identity from hosting, focus on high-scale aggregators (which are also debound from hosts), and use a data model which is more approachable to devs than RDF (json + lexicon).

Hi there, I'm one of the main community members working on Solid (TimBL mentions my apps in the article).

I can't speak for the whole community, but I recently wrote some of my thoughts on ATProtocol: https://bsky.app/profile/noeldemartin.com/post/3l7mj5glqey25

TLDR: I like ATProtocol, but there are a couple of things that don't make it as decentralized/independent as I'd like. Also, the fact that everything is public in ATProtocol makes it very different from Solid. Solid is all about data ownership, and many of the use-cases require privacy. Until ATProtocol has an answer for private data, I don't think it's even worth considering for most use-cases that Solid wants to tackle.