The ActivityPub standard needs your review!
A lot has happened in our work on standardizing federation with the W3C Social Working Group. ActivityPub is nearing Candidate Recommendation stage (we are aiming to reach that by October 11th), and in order to get there, we need public feedback! Here's a mailing list post explaining how you can help, though in summary:
- Reply to this thread!
- File issues on the issue tracker
- Email Chris Webber, personally (though know that I'll be putting your comments publicly on the social working group wiki, though you can be anonymous if you like): send to cwebber AT dustycloud DOT org, with "ActivityPub" somewhere in the subject.
- Send to the public-socialweb-comments list
Thank you! Your feedback is greatly appreciated! Here's to an interoperable federated social web!
Please note: The link to the editor's draft has changed. It's now here. Thanks!
Matt Molyneaux, sazius, Tyng-Ruey Chuang, Claes Wallin (韋嘉誠) and 3 others likes this.
sazius, JanKusanagi @identi.ca, Claes Wallin (韋嘉誠), mnd and 5 others shared this.
OMEMO implements the encryption of Signal, just like WhatsApp does these days. It really beats OTR and PGP.
mray INACTIVE at 2016-09-29T13:19:56Z
Christopher Allan Webber likes this.
it supports multiple devices!! have you ever tried to use OTR with multiple devices? Also the key management is way easier than PGP
mray INACTIVE at 2016-09-30T18:05:46Z
Claes Wallin (韋嘉誠) likes this.
Partially reviewed now =)
I created an issue for small typos and redundancies.
When I get the time, there are other things I'd like to discuss, like a specific note about the responsability of the clients when handling addressing of replies, and a point about how posting to only "Public" makes the object publicly viewable but not sent to anyone.
This comment will serve as a self-reminder =)