Has anybody thought about using a simplified variant of #ActivityPub ("ActivityMesh" perhaps?) on a #Reticulum network mesh? Of course, it can't be AP per se for several reasons. There was a talk about the Meshiverse a few years ago at FOSDEM. This could support bridging the Fediverse and the Meshiverse. https://archive.fosdem.org/2026/schedule/event/KUZUWX-off-grid_communication_cyberpunk_and_autonomy/
1 Boost
0 Likes
@mro I agree. Maybe "transport-efficient restricted subset" is a better phrasing than "simple". I also agree that defining and scoping the ActivityMesh goals would be a challenge. It certainly wouldn't be the "everything to everybody" BBoM currently defined in the AP specs.
@Steve_Bate
in case of #simple, count me in.
And remember, the #Fediverse is neither limited to #Mastodon, nor #ActivityPub.
I don't know about that. Simple does not mean easy, it can be hard. Just like any app dictates the AP flavor it understands, where connecting them together interoperably becomes complex, you might specify an AP protocol overlay that only interoperates with itself, and *then* build apps / solutions on top of that. So you have the ability to keep things simple. It can still be 100% W3C compliant, yet not fedi-we-have compliant out of the box.
Hi @Steve_Bate
I think #AP and 'simple' are conflicting goals. First would be to focus on ends to target. AP is a mixed bag of everything. There is no 'simple' this way.
P.S.: and I love simple.