How Nomadic ActivityPub (FEP-ef61) compares to other protocols?
I made a table:
https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md#protocol-comparison
How Nomadic ActivityPub (FEP-ef61) compares to other protocols?
I made a table:
https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md#protocol-comparison
@silverpill (added @jupiter_rowland)
Very interesting, thanks for the link!
I've recently started testing Holos, do you know about it? It seems to me (not a dev) that there are similarities, I hope you don't mind me tagging @HolosSocial to ask if there's something common to any of the listed projects and FEPs with Holos.
https://holos.social/how-it-works
Perhaps it merits a mention in the comparison table?
Thanks to all involved, nomadic/portable fediverse identities is a very exciting prospect.
@jandi @HolosSocial @jupiter_rowland
The similarities are superficial.
Holos is a regular ActivityPub application, where user's identity is bound to a domain name. Having a Holos account is equivalent to running a single user instance and doing continuous database backups. The difference is in the software architecture, not in the protocol: the database is located on user's phone instead of the machine where the server is running.
The how-it-works page also talks about cryptographic keys "never leaving your device". This is just misleading marketing. The location of the keys is irrelevant, because keys in ActivityPub are identified by URIs, and what an URI resolves to is controlled by a person who controls the server frontend and the domain name.