@cwebber, would you suggest that we, as a community, gather the various ActivityPub extensions together, and every ActivityPub server implements the whole AP spec and tries to support extensions, and every AP client implement the spec and tries to support extensions?
For example, I’m working on a federated project hosting platform (a forge). And one of the decisions I face is: Do I want it to implement the whole AP feature set, including the social stuff, or focus only on project hosting things? For example, one of these social features is authoring messages in which the recipient actor is a person, i.e. sending messages (public or private) to other people. This sounds like a basic feature, but it seems forges tend not to have it! I couldn’t find it in GitLab, and in Gogs, and it seems githu8 once had it but removed it years ago.
So, do I leave that feature to other servers to handle (i.e. ask people to use email / IRC / Matrix / Mastodon / Pleroma / etc. to exchange messages), or do I still implement this feature (and all the other social features) so that my software, in addition to handling projects and repositories and so on, also implements a full social server just like Mastodon?