@cwebber @mray You succeeded admirably, it's one of the easiest to readily comprehend protocols I've ever seen.

Which is why you didn't hear from me until *after* the bulk of that crypto extension first draft was finished. ;)

@cwebber @mray Very nice! Making things easy to follow is a lot of work. Thanks.

@cwebber thank you very much for all that work. as someone who worked on the W3C Mobile Web Initiative way-back-when, I super-appreciate what perserverence and hard work went into developing that consensus over & over, and then writing coherent explanations.

and by “thank you”, I very much mean plural ;^}

::chefs_kiss::

@cwebber

Wow, this is really great. Easy to understand and useful. Thank you.

@mray

@cwebber @mray this is very interesting 🤔 looking forward to learn more. Do you know about any good conference talks about it?

@cwebber @mray

The example given in this tutorial is of a private message. Which raises a question: if A is following B and B makes a _public_ post, will A be pulling it from B's outbox or will B be pushing it to A's inbox?

If B has a million followers, push would be very expensive for B's server. And if A needs to pull the feeds of everyone s/he follows, it's again expensive and wasteful and likely high-latency.

@cwebber @mray I ran across this last week. Maybe a little less dense than the actual docs for folks just looking for a more simplistic overview. https://activitypub.rocks/

@cwebber @mray This overview is (and has been) fantastic. I’ve always had a harder time digesting W3C specs (just in general, not just ActivityPub), but a lot of that is just necessary complexity, since it has to be robust and work in a lot of cases. I’ll need to steel myself and give it another try.

@cwebber @mray

I've read it. It is indeed an easy to read specification.

@cwebber @mray Does Mastodon leverage ActivityPub?

@cwebber Ooh was looking at spec a few days ago and thinking it doesn't look too dry and inaccessible! Tempted to do some playing about, so thanks for your work!

@cwebber outstanding work, congratulations to all involved. By the way, would you happen to know what is the easiest way to get the latest version of the full spec in printable format?

@cwebber @mray TBF such nice narratives in specs are sort of rare.

@cwebber @mray I think this is by far the *nicest* W3C spec I’ve ever read