New blog post: How to implement a basic ActivityPub server https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/
@Gargron it's really useful, I was thinking about implementing a lightweight server in rust (for fun and to learn rust) and that's precisely what I needed! Although the w3c paper is quite digestible it's good to have an explanation about signatures and all.
So thanks! If you post more details about following I would find it very helpful!
@bortzmeyer @saxnot That, and the fact I literally was part of the AP design sessions, why would I violate the spec with my implementation if my implementation literally shaped the spec. The lie originates from the OStatus days, and even then it wasn't true, GNU social wasn't 100% compliant with the written specs and I refused to repeat those mistakes.
@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.