“#ActivityPub, a protocol that aims to unify federation and client interactions within decentralized social networks, reached its W3C Recommendation state recently. Along with their state change, they got a bit of press coverage, and obviously, the specification is known within my bubble. Naturally, as I am one of the people behind #diaspora*, I get asked what I think about ActivityPub and whether diaspora* will change its implementation to be compatible with it. I could be cheap and just link to xkcd-927 and be done with it, but that would neither be useful to anyone nor respectful towards all the people who worked on ActivityPub, so here we are.”
▻http://schub.io/blog/2018/02/01/activitypub-one-protocol-to-rule-them-all.html
Good summary of the issues with ActivityPub. One of my favorites: you cannot really build standard software for distributed #social_networks because they have vastly different semantics. In practice, most users of ActivityPub (such as #Mastodon) will certainly extend the protocol a lot and therefore won’t be compatible. Another one: ActivityPub leaves too many things unspecified (such as the entire field of authentication and confidentiality).
So, if someone requests SeenThis to implement ActivityPub, this could be used for a short reply.
