New blog post: How to implement a basic ActivityPub server https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/
@bortzmeyer They're not in the spec! The spec left them "up to the implementation"
@bortzmeyer It's both bad and good. Lack of directions for transport and authentication layers means ActivityPub could be used over udp or websockets. Of course that's little use to us, since those layers being incompatible would cut us off.
@bortzmeyer That's us!
@bortzmeyer I mean, you're kinda right because Mastodon predates ActivityPub and became popular before that. But why is it a failure? We have Mastodon, Misskey, Pleroma and PeerTube talking to each other using ActivityPub, Webfinger and HTTP Signatures. They may not all be written down in the ActivityPub spec because it's "up to the implementers" but they're all real standards!
@bortzmeyer ActivityPub is the language, and to use the language we need a transport layer. The designers of ActivityPub wanted that separation because it would not be possible to push the standard through W3C otherwise. What you're looking for is some kind of ActivityPubSuite standard.
