The biggest problem for peer to peer ActivityPub is the fact that ActivityPub is primarily a "pull" protocol. You need to fetch a remote actor before interacting with it. This is not feasible in the environment where nodes are intermittently online.

What if we used a special activity to request objects? I've described this idea in more detail in Asynchronous object retrieval:

https://codeberg.org/silverpill/feps/src/branch/main/aef6/fep-aef6.md

I think this mechanism, if combined with self-authenticating objects, should make ActivityPub compatible with store and forward protocols.

#p2p #dtn #fep_ef61

en

Replying to @⁨silverpill@mitra.social⁩

@silverpill I don't even want it to be p2p, I think p2p has considerable downsides to a federated structure. Yes I like p2p networks as a fallback in authoritarian regimes where you can't reliably host common resources pools, but when this is possible a federated structure has significant advantages both technical and social (shared ressources like server/data space, outsorced administration, shared moderation, community coherence, etc. etc.).