[guardian-dev] Messaging Moving Forward

[Patrick Baxter]

I also like the idea of supporting the goals of #1 but also working to
build a competitive stack ala #2 that retains branding and
'just-working' ability across many platforms. This way you can target
the audience that would flock to both groups. I guess the question
remains if these are conflicting goals or not.

Federation and XMPP give you a single namespace for people to use
which I think is invaluable. The other concern is supporting client
standards for both encryption AND verification/authentication.

I like the idea of bringing everyone together who is interested in
open-secure messaging and create a giant platform. If they don't want
to be part of the same branding/platform then work on interoperability
and client standards. It'd be nice if everyone could get to the point
of not just using XMPP to have a single namespace, but also supporting
the same encryption AND verification/authentication standards.

Keep the communication open and standardized and work for
compatibility to those with the same goals (Cryptocat, Whispersys).

On Fri, May 17, 2013 at 2:39 PM, Dominik Schürmann
<dominik at dominikschuermann.de> wrote:
> Hey folks,
>
> take 1 and some parts of 2.
>
> I think only supporting existing standards is not sufficient, as it is
> too complicated for the average user to sign up to (or set up your own)
> Jabber/SIP server and configure your apps. Integrated solutions like
> most design decisions (not all) of Redphone, which uses one
> infrastructure, standardized ZRTP key exchange, but non-standard session
> protocol are the way to go. These design decision provide usable crypto.
> What it is lacking in my opinion, is to educate the user about how to
> use ZRTP properly.
>
> Redphone is just an example for combining (1) and (2) and open source is
> one basic requirement for these kind of software (they should release
> the server source!).
>
> While these integrated solutions are nice, interoperability is important
> to reach a wider audience, as most users already have XMPP accounts for
> example (-> Gibberbot).
>
> Ad (3): In my opinion it's a waste of time and effort to code fpr closed
> ecosystems. These closed systems are changing too rapidly. Google Talk
> migrated to Hangout just these days, Whatsapp changes their
> authentication every 3 month (because their security sucks). What can be
> done is using these closed systems as a side channel to initiate
> connections in open systems.
>
> Thanks Guardianproject, you are doing most things right!
>
> - Dominik
>
>
> _______________________________________________
> Guardian-dev mailing list
>
> Post: Guardian-dev at lists.mayfirst.org
> List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev
>
> To Unsubscribe
>         Send email to:  Guardian-dev-unsubscribe at lists.mayfirst.org
>         Or visit: https://lists.mayfirst.org/mailman/options/guardian-dev/patch%40cs.ucsb.edu
>
> You are subscribed as: patch at cs.ucsb.edu
>