<div dir="ltr">I'm sure this was all hashed out when the change to Signal notifications was made, but I'm not a big fan of showing the name or the message in notifications. It's fine that I can control what's displayed in *my* notifications, but as the sender I also have an interest in what's displayed in the recipient's notifications, and I have no control over that. I'd like to know that when I send someone a message, only he can read it, but when messages might be pushed to the lock screen of a locked phone, I don't know that. If my communication partner's phone falls into the hands of an adversary, I may send a message that incriminates me or him that the adversary receives instead of the intended recipient.<div><br></div><div>I suppose I could always start off by saying, "Hey, are you there?" and wait for a response before I say anything else, but that makes things a lot more synchronous than they need to be.<br><br><div class="gmail_quote"><div dir="ltr">On Mon, Feb 22, 2016 at 2:08 PM Jason Strange <<a href="mailto:jason@technowizardry.net">jason@technowizardry.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
There are options to limit the information displayed in
notifications (To "Name and message", "Name only", and "No name or
message"), and if you have a Signal passphrase set, whenever Signal
is locked, the notifications read as Locked Message. My Android is a
little rusty, but you can review the notification system here to
learn more:<br>
<br>
<a href="https://github.com/WhisperSystems/Signal-Android/tree/master/src/org/thoughtcrime/securesms/notifications" target="_blank">https://github.com/WhisperSystems/Signal-Android/tree/master/src/org/thoughtcrime/securesms/notifications</a></div><div bgcolor="#FFFFFF" text="#000000"><br>
<br>
<div>On 2/22/2016 11:02 AM, Tony Arcieri
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Mon, Feb 22, 2016 at 10:21 AM, Ali
Aydin Selcuk <span dir="ltr"><<a href="mailto:aliaydinselcuk@gmail.com" target="_blank">aliaydinselcuk@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Message contents are visible from the
notification bar, which should be transmitted over
Google's or Apple's push notification servers.<br>
<br>
We just can't see how this is compatible with the
end-to-end encryption feature of Signal. <br>
<br>
Are we missing something, or is there something
fundamentally wrong here?</div>
</blockquote>
<div><br>
</div>
<div>I do not work for or speak for OWS, but that said...</div>
<div><br>
</div>
<div>When Signal first launched, the push notification
handler just displayed "New Message". This is annoying
from a UX standpoint.</div>
<div><br>
</div>
<div>I believe they later added support for decrypting
messages within Signal's push notification handler.</div>
<div><br>
</div>
<div>I believe it's also an option you can toggle on and off
(so as to e.g. prevent someone who steals your phone from
seeing these messages)</div>
</div>
<div><br>
</div>
-- <br>
<div>Tony Arcieri<br>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Messaging mailing list
<a href="mailto:Messaging@moderncrypto.org" target="_blank">Messaging@moderncrypto.org</a>
<a href="https://moderncrypto.org/mailman/listinfo/messaging" target="_blank">https://moderncrypto.org/mailman/listinfo/messaging</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
Messaging mailing list<br>
<a href="mailto:Messaging@moderncrypto.org" target="_blank">Messaging@moderncrypto.org</a><br>
<a href="https://moderncrypto.org/mailman/listinfo/messaging" rel="noreferrer" target="_blank">https://moderncrypto.org/mailman/listinfo/messaging</a><br>
</blockquote></div></div></div>