Why the #OMN works with #ActivityPub – And why we need a bridge to #p2p

Let's look at this. #ActivityPub is not a product. It’s not even really a “protocol” in the narrow, rigid sense that vertical tech likes to imagine. ActivityPub is a shared vocabulary, a public language for moving meaning and connection across the #openweb. It gives you nouns and verbs, and the community defines the grammar through lived use. This is why the #OMN works with ActivityPub, a metadata and meaning layer, not a platform, flows, not silos. ActivityPub is the widely deployed […]

https://hamishcampbell.com/why-the-omn-works-with-activitypub-and-why-we-need-a-bridge-to-p2p/

@info We may not need bridges because ActivityPub can be extended to work in peer to peer mode.

This possibility was unlocked by nomadic identity: https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md

ap-next/nomadpub.md at main

ap-next - ActivityPub Next

Codeberg.org
@silverpill There is a server to server #API could that work for #p2p? Will have a look at the nomadpub
@info All current implementations use HTTP but nomadic AP (FEP-ef61) was designed to be transport-agnostic, so in theory HTTP can be replaced with a different transport protocol.
@silverpill I was thinking of “stupid” as in running a common, shared database of objects sharing flows, which can cross either protocol. This will likely break some security in both protocols, the question is this a #block or not. The #OMN project is public #4opens, so security is based on trust with only minimal hard tech.