@[email protected] I worked on Solid at Inrupt on the javascript sdk team, and the biggest problem solid has is learning curve, which is why I've been saying "AT Protocol is a bunch of the solid ideas but waaaay simpler learning curve" partly because you don't need to mess with json-ld

That and not even Inrupt appear to publicly do Solid anymore, they're all wallets now, apparently?

@thisismissem @mfru

In your opinion, did you feel that the complexity of Solid was ONLY due to JSON-LD?

Or, were there other (non- JSON-LD) things that made it complex, too?

@reiver @thisismissem @mfru

I made a diagram yesterday that contrasts #ActivityPub and #SolidProject that is I think interesting to consider.

In the past I've been very active on the Solid forum, and tried to get a collab going with #SocialHub community. A number of points that existed then, are still issues today I think.

Like, though anyone could participate in the standards process via chat, the Solid team and Inrupt were not really interested in their community, hardly giving attention while people were building interesting stuff there.

Also at the time basically all available code was Javascript, making Solid uninteresting or hard to access for other language devs.

But I think biggest issue was that Solid didn't know what it was. It was positioned as 'personal data vault' on the landing page then (but not using this term), but was 'secretly' TBL's desire to reboot the #SemanticWeb. The new web would be all 'Solid apps'. But the adoption strategy for that didn't exist.