Implementing Murmurations protocol
In the long run, it's unfeasible to keep adding individual service providers. We need an uniform JSON-based protocol that informs Keyoxide/DOIP projects about basic member identity information (mostly username and associated key fingerprints).
In their protocol repo, they specifically mention "economy organisations and commons-building projects", I do assume that's just an example. It also shows geographical mapping of the data, again I hope it's just related to the example they are using.
As you can see, I still have a somewhat hard time wrapping my head around the entirety of the protocol and, more importantly, all the implications of its design. Hope it suits the needs of the project, it would save a lot of future effort.
Thanks for creating this issue @yarmo .. I made a crossref to where I am in contact with people from the Murmurations team: Improvement to FEDERATION.md convention: Murmurations.
Note that Murmurations also supports JSON-LD formatted profiles.
Deleting a branch is permanent. It CANNOT be undone. Continue?