As part of my quest to expand the use of Solid for web applications – and start building bridges with the AT Protocol community – I’ve launched an application directory for ATProto and Solid apps:
Right now there are two ways to add a listing;
JSON-LD blob on your apps homepage
ATProto record on your PDS
I’m working towards a third that works like #2 for solid folks;
3. RDF statemetns on your Solid POD
I would love to see some more Solid apps on here. What do you y’all think about the project and the idea?
I’ve also been curious about ATProto for a while, but as far as I know you can only store public data in PDSes, right? In Solid, you can have both public and private data, but I think it’s more common to have private data (at least with the apps I’ve seen), so I’m not sure about that idea of bridging both… But it’s interesting, keep us updated on that.
About application listings, in Solid there is also another way that is pretty common to declare applications, in fact it’s a requirement for logging in sometimes. That is called the “client id”, and it’s a document similar to web manifests for PWAs. I’m not sure there is any way to auto-discover them (they aren’t usually linked in the header or anywhere that I know), but if you get the link, they are a pretty good document to describe the app.
Thats a good idea to accept links to that JSON doc that… did not occur to me for some reason.
And yeah, the ATProto stuff is VERY much “public data, shared discovery” vs “permissioned data, locally discoverable” of Solid. Getting them to play nicely with each other only works for Public data, but the idea of “bring your own ID and store your own data” is a common ground between them.
I’ll add the client id json parser, then your apps could be on there easy!
Synara was submitted by me. I’ve also extended the App directory at PrivateDataPod.com to include the ability to add apps using the same method and approach as the store.