As someone who creates ActivityPub services, it's often a puzzle to figure out exactly how someone else's service federates. Like, what does service X do when I send it a Delete/Note activity?
In an attempt to be a good citizen, I've drafted up a FEDERATION.md file for my fediverse event organizing service I'm working on. Here it is:
I've also started a meta-discussion about how we might start documenting this stuff generally:
But it can be hard to navigate, so I wrote a guide to navigating it here:
I agree that we need a solid place where we discuss the Codes and Codices of Interoperability.
@redaktor (my baby) has got the same problem with the "multilanguage" and "topics" and "OAuth weblayer" - commented at the thread.
It sounds you don't want mastodon but one of the other software where the UX is more organic, just like yak wool ;)
I am doing https://socialhub.activitypub.rocks/c/software/redaktor-me/22
Server - 60% ready.
Basic components - ready
overall 50% ready before release
@darius for what it worth, this is what we have for Funkwhale: https://docs.funkwhale.audio/federation/index.html
Maybe we could agree on a nodeinfo field to put a link to this kind of documentation?
@eliotberriot that's very nice! I will read this in more detail when it's not midnight
@darius sure! Also, if we can agree on a format to describe activities, we could also expose this in nodeinfo directly, e.g:
SupportedActivities: [Create/Event, Delete/*, Follow/*]
@darius I’ve wondered this a LOT! What a great idea
@darius Sounds Great ! Good luck!
@darius excellent idea
Hometown is adapted from Mastodon, a decentralized social network with no ads, no corporate surveillance, and ethical design.