Added Nomadic ActivityPub page to the ap-next repository:
https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md
This is a brief summary of the work we've done. Feedback is welcome!
Discussion
Loading...
@silverpill Yay, I’m very excited that this is moving forward
Am I correct that `did:key` implies that users will be able to BYOK (bring their own keys) to verify the identity of their content, no matter which Fediverse instance they’re using?
Am I correct that `did:key` implies that users will be able to BYOK (bring their own keys) to verify the identity of their content, no matter which Fediverse instance they’re using?
Ideally we have a hybrid solution, where the keys could be held in either or both a client and a server.
That way you could maintain your own identity on your own device, such as a computer or phone, without needing a server. But, you could also have a clone of your identity on a server, which provides a backup in case your personal device is lost. Or vice versa.
cc: @ Eugenus Optimus 🇺🇦 @silverpill
@smallcircles @steve@helge This forum is not federated, right? Do you plan to enable ActivityPub federation?
@smallcircles @steve@helge I've been working on vNext unofficially for quite some time, because the exploration of nomadic identity forced me to rethink every aspect of the protocol. This work led to the creation of "New Year Roadmaps" (2024, 2025), several FEPs and the developer guide. Now I am making it more official with ap-next, and subtly inviting others to contribute.
I may collaborate with other groups, but there have been plenty of them and all fizzled out very quickly.