There is an interesting paper on using DID in combination with ActivityPub [0] presented in the 'Rebooting the Web-of-Trust' [1] event in Fall 2017. > Activity

There is an interesting paper on using DID in combination with ActivityPub [0] presented in the 'Rebooting the Web-of-Trust' [1] event in Fall 2017. > ActivityPub implementations at the present moment rely on HTTPS as their transport, which in turn relies on two centralized systems: DNS and SSL certificate authorities. Is there any way to bring self-sovereignty to the federated social web? > Thankfully there is; ActivityPub was written intentionally to be layerable on any protocol that can support HTTP GET and POST verbs. The Decentralized Identifiers specification looks to be a good fit for ActivityPub. [..] > Here we see an example of Alyssa's profile that is entirely free of traditional centralized DNS authorities. We were able to look up Alyssa's object via her DID, but we still have access to all her endpoints, which in this case are pointing to Tor Hidden Services. No central DNS required! [0] https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust-fall2017/blob/master/topics-and-advance-readings/activitypub-decentralized-distributed.md#distributed-identity https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust... [1] http://www.weboftrust.info/ http://www.weboftrust.info/