Continuing the DoOcracy

[silverpill]

@helge

Looking at the Account Migration, I was back to clicking myself through many places of documentation, i.e. in addition Mastodon, Mitra, Pixelfed, Lemmy.

FEDERATION.md

It’s a proposed standard for documenting protocol extensions. Mastodon repository also has one: mastodon/FEDERATION.md at a9b5598c97fc4d3302b61b260097ef41c2ebe377 · mastodon/mastodon · GitHub, and here’s Smithereen’s: Smithereen/FEDERATION.md at 71bcc73b62743e864463840922b50771f025f0c2 · grishka/Smithereen · GitHub.

I think this was a great idea, and it needs promotion.

Documenting federation behavior in a semi-standard way?

TL;DR, please check out FEDERATION.md and tell me what you think about it. Context: I am in the process of federating an existing service for organizing events and meetups called gath.io. The federated currently version lives at events.tinysubversions.com, and the source code for my branch is available here. Because I’m building a federated service, I felt like I should add the documentation that I wish other federated services had: namely, something that describes how the server responds to a…