I think a lot of this stuff will rely on a more formal spec like https://github.com/solid/solid-spec https://github.com/solid/solid-spec to be useful. For iden

I think a lot of this stuff will rely on a more formal spec like https://github.com/solid/solid-spec https://github.com/solid/solid-spec to be useful. For identity, there's https://github.com/solid/solid-spec/blob/master/solid-webid-profiles.md https://github.com/solid/solid-spec/blob/master/solid-webid-... Right now I'm particularly interested in https://github.com/solid/web-access-control-spec https://github.com/solid/web-access-control-spec although I think it's incomplete when it comes to data portability and access control. From what I've seen on re-decentralizing the internet, access control is either non-existent, or relies on a server hosting your data to implement access control correctly. What if, in the WAC protocol linked above, instead of ACL resources informing the server, we could have ACL resources providing clients with keys to the encrypted resource (presumably wrapped in each authorized agent's pub key). Host proof data is a necessity for decentralized social networking IMO, even if the majority of agents would happily hand their keys over to their host.