Bwaaaahahaha this classic exchange.
web.archive.org/web/2017021919…
@lambadalambda What's going on on your instance?
You think I'm going to ban / moderate someone because one user on mastodon.social had to read a DISSERTATION on ancap politics?
Around the time Mastodon entered the room, ActivityPub was already brewing in the background. Why?
1. @evan wanted to take pump.io lessons learned to the W3C
2. @cwebber wanted federation in MediaGoblin
In the end, ActivityPub almost didn't become a W3C recommendation due to time constraints if it hadn't been for the fact that
3. @Gargron wanted better privacy controls and federated DMs in Mastodon, and less papering over the gaps in OStatus
@clacke @gargron @evan This is true but I also want to highlight that @erincandescent wrote the first draft version of the spec (transformed from the Pump API), @tsyesika carried the spec through the first half of standardization, and I carried it through the second half, with major work / help from @rhiaro... and @VamptVo wrote the first draft version of ActivityPub in Mastodon which Gargron completed! Not to mention all the other people in the SocialWG, etc :)