The obvious choice for ActivityPub’s birthday would be the 23rd of January 2018 - the day it was annointed as a W3C recommendation. That doesn’t seem quite right though - its not as if the spec came into existence in any sense upon that date. In fact, Mastodon implemented it before thne.
There are several possible dates you might pick, but for me it will always be September 5th 2014 - when I committed the first sketch of a specification I called ActivityPump and pushed it to Github
It wouldn’t be until November that I actually submitted (a revised and enhanced version of) that draft to the working group, but even then I had the very nucleus of the specification written down.
Happy 10th birthday, ActivityPub. 🍰
Here be a first draft · w3c/activitypub@f510032
Contribute to w3c/activitypub development by creating an account on GitHub.GitHub
reshared this
Tim Chambers
in reply to Erin 💽✨ • • •Erin 💽✨
in reply to Erin 💽✨ • • •reshared this
Rokosun reshared this.
Erin 💽✨
in reply to Erin 💽✨ • • •Sometimes I ponder: If I’d had a detailed security mechanism in that first draft, could I have saved everyone a lot of pain?
Ah well, hindsight.
reshared this
Rokosun reshared this.
just small circles 🕊
in reply to Erin 💽✨ • • •I wonder to what extent you feel that fediverse is evolving in the right direction. Is it still moving to become the future of social networking, or is the ad-hoc code-first and reconcile-protocol-decay-later, too detrimental for that? Stifling progress today.
Depending on the answer, are you in favor of making a clean break for a protocol vNext? Take the current fedi as proof-of-concept and great prototype to distill the lessons-learned and progress with fresh perspective.
Oblomov
in reply to Erin 💽✨ • • •Erin 💽✨
in reply to Oblomov • • •Oblomov
in reply to Erin 💽✨ • • •Oblomov
in reply to Erin 💽✨ • • •lostinlight
Unknown parent • • •