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.
Also, in French, https://asso.framasoft.org/nextcloud/s/geoJBDycra8P8AX#pdfviewer
Also in French, my talk and article at JRES in november :-)
@tedu it's been kind of interesting/frustrating for me, someone who's coming into the spec from the non-tech side (despite having a modicum of tech literacy) to see how many "gotchas" there are. tiny misimplementations and idiosyncracies in particular, but some big-picture things too, like making bad assumptions/decisions.
(mastodon in particular, with some of the limits it takes for granted, and how it ends up holding back the rest of the network, but not just mastodon of course...)
@tedu but for starters, even a simple "we use these properties for these things" would be a good step forward for trying to figure out how each implementation treats the http/json(ld) stuff. or "we accept these properties and transform them like so".
social.coop is a cooperatively-run corner of the Fediverse. The instance is democratically governed by its members, who generally share an interest in the co-op model, but topics of discussion range widely.
Our instance is supported by sliding scale contributions of $1-10/mo made via Open Collective. You must have an active Open Collective account to apply for membership; you may set one up here