I think I've finally seen the light of the #SemanticWeb.
I think web browsers should give users a way to register apps to handle displaying certain #RDF schema types.
E.g. if I open an ActivityStream URL, the browser should load my preferred client in the same way that clicking a PDF in my filesystem will open up my PDF viewer.
Users would then be able to bring their own interfaces to data instead of relying on some closed source proprietary app interface.
Also opens the door to mixing data
@mauve Would this work in some non-rubegoldbergian way for nonpublic ActivityStreams data? (Do you know if it would be trivial to make it work via the proxying described in ActivityPub Client-to-Server?)
@robryk I think Client-server might be a good start. I'm thinking a web extension yhat lets you register apps to redirect to would be a good start. Maybe you'd also need auth tokens or cookies sent to the app as part of that?
I think the main limiting factor would be the lack of search in RDF, so if endpoints provided Triple Pattern Fragments endpoints it'd get us the most bang for our buck.
