ActivityPub needs something like the Busy Developer's Guide to SOAP we did in 2001.
https://web.archive.org/web/20050204072726/http://www.soapware.org/bdg
@dave Gosh, yes. Even the simplest documentation I've found seems overly complex. When I've mentioned this, defenders say they don't want people implementing ActivityPub without thinking everything through. Which eliminates busy developers!
@josephholsten @dave I guess I'd make a distinction between things that are irreducibly complex and things that are arbitrarily complex.
I don't think anybody can credibly claim that ActivityPub is irreducibly complex. It's really hard to make arbitrarily complex things simple, but that's key to widespread adoption.
Which is why Mastodon is what most people know of the fediverse. It's simpler.
@pwinn @dave sitting on it, I’m coming at this from a server implementor/operator’s perspective. We should absolutely have a busy dev’s guide for building activitypub clients.