The missing fediverse documentation:

When I post a toot, what happens? What steps does my server take to send that toot to other servers? When people read that toot, what steps does their server take? Detailed all the way down to http calls and json-ld.

I don't mean what happens for Mastodon (or Pleroma), I mean for any fediverse-compatible server. I also don't mean ActivityPub or Lightpub, I mean what happens today, in reality, not what happens in some idealized ivory tower whitepaper.

@trwnh @gdorn

This was a quick effort, but I think I've got all the back and forth covered. It is difficult to know what's unclear when writing, however.

@tedu @gdorn yeah stuff like this is very helpful for readers, but to a certain extent it is also the responsibility of projects to detail this own stuff in their centralized docs. it would certainly help when trying to deal with compat issues, to not have to trudge through various issue trackers.

@trwnh oh, yes, I've been trying to at least casually mention various quirks in case somebody stumbles upon them. Not sure how useful that is, because all the little details aren't linked in one place, but I hope at least bringing a few more things into the light will eventually lead to discovery.

As an implementer, it can be annoying but you eventually figure things out. I think the network will work better with more user literacy, even for people who never go near the code. Tough call to say what should be considered essential knowledge, however I think it's probably shifted towards too technical.

@tedu @trwnh With end-users suggesting new features and behaviors to the various projects, it benefits everybody if they understand the protocol better.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!