What? The fuck.
> On Apr 19, 2016, at 12:00, [email protected] wrote: > > Send guardian-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.mayfirst.org/mailman/listinfo/guardian-dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of guardian-dev digest..." > > > Today's Topics: > > 1. Re: New post on ChatSecure Push! (Pranesh Prakash) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 19 Apr 2016 11:22:05 +0530 > From: Pranesh Prakash <[email protected]> > To: Nathan of Guardian <[email protected]>, > [email protected] > Subject: Re: [guardian-dev] New post on ChatSecure Push! > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Dear Nathan and Chris, > I'm not very sure about the viability of the solution that has been > rolled out. > > From what I understand, if Alice on Example.org using Client Y is > seeking to communicate with Bob on Dukgo.com on Client Z, then for Bob's > phone to support push messages with: > > - XEP-0357, Dukgo.com and Client Z need to roll out support for XEP-0357. > - Chatsecure Push Protocol, Client Y and Client Z need to roll out > support for CPP. > > Push is really needed only if you're using a mobile client, and > specifically if you're using iOS (since on Android, it's never really > been a problem). I'd argue it might be simpler to get the largest > server instances (Dukgo.com, jabber.ccc.de, etc.) to support XEP-0357 > and get people to use an XEP-0357 capable client on iOS (say Chatsecure > and Monal) than to get all those who correspond with those clients to > *also* support a special something like CPP. > > Given that desktop clients like Pidgin have not been adding support for > new features (even carbons!) for years, I doubt we'll ever get to a > position where CPP would really work well. > > Further, by pushing a non-standardized solution, one of two signals is > being sent: > > 1. Chatsecure devs hope that its userbase ends up meaning other > clients also adopt this. > 2. Chatsecure devs don't really care who else adopts this, as this > would primarily be used for Chatsecure-to-Chatsecure conversations. > > I hope it is (1). While Conversations devs have rolled out new features > (HTTP Upload, OMEMO), they've sought to work to standardize through the > XSF by publishing draft XEPs. > > While I like the ingenious and decentralized nature of the solution > Chris has crafted (where the only servers that need to be involved are > the push servers run by the client dev), I do hope you'll work to get it > standardized and adopted by others. And I also hope Chatsecure (esp. > for iOS) will add support for XEP-0357 too. > > Also, I'd love to learn why you feel the other way, as I might well have > misunderstood or missed something. > > Regards, > Pranesh > > Nathan of Guardian <[email protected]> [2016-04-18 09:13:42 > -0400]: >> >> If you haven't read it you should: >> https://chatsecure.org/blog/chatsecure-v32-push/ >> >> "With the release of ChatSecure iOS v3.2, we have enabled the first >> phase of a new form of push messaging that is decentralized, >> interoperable, and reduces identifiable metadata. Users of any app >> compatible with the ChatSecure Push protocol can send push messages >> across app boundaries, starting with the latest release of ChatSecure >> iOS and the next version of Zom Messenger. These push messages currently >> contain no content and are simply a way to wake up the receiving client >> for ~20 seconds." >> >> Important work by Chris and the ChatSecure team... having a >> privacy-preserving, decentralized push mechanism on iOS is both >> essential and cool. >> >> +n > > -- > Pranesh Prakash > Policy Director, Centre for Internet and Society > http://cis-india.org | tel:+91 80 40926283 > sip:[email protected] | xmpp:[email protected] > https://twitter.com/pranesh > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 801 bytes > Desc: OpenPGP digital signature > URL: > <http://lists.mayfirst.org/pipermail/guardian-dev/attachments/20160419/d501dfeb/attachment-0001.sig> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > guardian-dev mailing list > [email protected] > https://lists.mayfirst.org/mailman/listinfo/guardian-dev > > > ------------------------------ > > End of guardian-dev Digest, Vol 70, Issue 8 > ******************************************* _______________________________________________ List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To unsubscribe, email: [email protected]
