<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Dec 16, 2014 at 11:19 PM, Ralf Senderek <span dir="ltr"><<a href="mailto:crypto@senderek.ie" target="_blank" onclick="window.open('https://mail.google.com/mail/?view=cm&tf=1&to=crypto@senderek.ie&cc=&bcc=&su=&body=','_blank');return false;">crypto@senderek.ie</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Dec 15, 2014, at 5:37 PM, Tony Arcieri <<a href="mailto:bascule@gmail.com" target="_blank" onclick="window.open('https://mail.google.com/mail/?view=cm&tf=1&to=bascule@gmail.com&cc=&bcc=&su=&body=','_blank');return false;">bascule@gmail.com</a>> wrote:<br>
<br>
</span><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ideally encryption should be transparent to Johnny, and something Johnny's email provider can flip on<br>
</blockquote>
<br></span>
and off<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
transparent to him ...<br>
</blockquote>
<br>
What a revolutionary idea.</blockquote><div><br></div><div>The "revolutionary" part is that if the end-to-end extension is written correctly, transparently, and in an open-source manner, if Johnny's provider does this, it will notify Johnny </div></div><div><br></div>-- <br><div class="gmail_signature">Tony Arcieri<br></div>
</div></div>