<div dir="ltr">The <a href="https://github.com/redsolution/xabber-android/commit/1ed13b2625d444112d85b3170c78903a11851fae">Xabber icons</a> look good. The idea occured to me as i was writing my earlier reply, so it must have some level of commonality to it. I dropped it because a plain hinge was my idea of secure, which doesnt communicate anything in the way of verified or not. The checkmark is brilliant.<div><div><br></div><div>However the problem is present with the Xabber set. The <a href="https://raw.githubusercontent.com/redsolution/xabber-android/1ed13b2625d444112d85b3170c78903a11851fae/app/src/main/res/drawable-hdpi/ic_security_plain_24dp.png">first icon</a> makes unverified look quite similar to something that is locked down. Exactly the opposite.</div><div><br></div><div>If instead the top part of the lock is swung around the other way and there is an exclamation-mark on it, it will alert the user to something not being optimal. Attached you will find my idea of doing it.</div><div><br></div><div>But back to the earlier proposal. Do you all like the new logo? I hope it comes to use.</div><div><br></div><div>I enjoy both the OTR software and communicating with the people behind it, thank you all.</div><div><br></div><div>Allan Nordhøy (kingu)</div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 6, 2015 at 6:00 PM, <span dir="ltr"><<a href="mailto:otr-dev-request@lists.cypherpunks.ca" target="_blank">otr-dev-request@lists.cypherpunks.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send OTR-dev mailing list submissions to<br>
<a href="mailto:otr-dev@lists.cypherpunks.ca">otr-dev@lists.cypherpunks.ca</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.cypherpunks.ca/mailman/listinfo/otr-dev" target="_blank">http://lists.cypherpunks.ca/mailman/listinfo/otr-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:otr-dev-request@lists.cypherpunks.ca">otr-dev-request@lists.cypherpunks.ca</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:otr-dev-owner@lists.cypherpunks.ca">otr-dev-owner@lists.cypherpunks.ca</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of OTR-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: OTR-dev Digest, Vol 75, Issue 1 (Allan Nordh?y)<br>
2. Re: OTR-dev Digest, Vol 75, Issue 1 (Nick Guenther)<br>
3. Re: OTR-dev Digest, Vol 75, Issue 1 (Ian Goldberg)<br>
4. Re: OTR-dev Digest, Vol 75, Issue 1 (Peter Fairbrother)<br>
5. Re: OTR-dev Digest, Vol 75, Issue 1 (Ian Goldberg)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 6 May 2015 00:11:53 +0200<br>
From: Allan Nordh?y <<a href="mailto:epost@anotheragency.no">epost@anotheragency.no</a>><br>
To: <a href="mailto:otr-dev@lists.cypherpunks.ca">otr-dev@lists.cypherpunks.ca</a><br>
Subject: Re: [OTR-dev] OTR-dev Digest, Vol 75, Issue 1<br>
Message-ID:<br>
<CAMnoC=y6_Pi2W=bZSLXOEV4g61s=<a href="mailto:Cv3yEfAxG3ZRQBVyGCbtCA@mail.gmail.com">Cv3yEfAxG3ZRQBVyGCbtCA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
It started with me being exposed to what Pidgin uses as an icon to signal<br>
the nature of current OTR-connections.<br>
<br>
At first some heads (?) forming a crowd of three for cleartext<br>
conversations.<br>
Changing into one person with a warning-sign before it for unverified<br>
connections.<br>
Verified connection are displayed as just a pictogram of one person.<br>
For some reason this same icon changes and displays for IRC-chatrooms too,<br>
still with the OTR-settings for the last opened one-to-one conversation.<br>
<br>
I ventured into the the #otr IRC-room to report on a broken link on the<br>
site, and i also mentioned how the icon-background isn't transparent,<br>
knowing that its an easy fix. Thinking maybe there might be something<br>
better to do drop into its place alltogether.<br>
<br>
Then, shortly therafter: (21. march 14.03 +0100) jvoisin: we need a logo :<<br>
<br>
Many designs later, some of which were novel, but not good, I had maybe<br>
fixed what I set out to solve in that it would be an improvement over the<br>
current set of icons.<br>
Since that isn't good enough I made something that I think works for both<br>
icons and logo.<br>
<br>
Change the colours and you have all modes. Red for "not private", Yellow<br>
for "unverified" and Green for "authenticated".<br>
<br>
Or, still going with two different two designations; two megaphones, an<br>
envelpe with a questionmark on it, and maybe an envelope being handed over.<br>
<br>
Right now there are two instances of the same icon, one at the bottom next<br>
to the chat-field and another up top along with "OTR" in writing, on a<br>
different button to trigger the same menu.<br>
<br>
What was initially a weekend job of drawing and digitizing resulted in good<br>
feedback on one design, only to protract over a month, slowly but surely<br>
passing my own judgement, steadily holding up against attempts to improve<br>
it. Some pixel-fixes later and here we are.<br>
<br>
The design I made is my own, so I can license it however you please.<br>
<br>
-Allan Nordh?y (kingu)<br>
<br>
On Tue, May 5, 2015 at 6:00 PM, <<a href="mailto:otr-dev-request@lists.cypherpunks.ca">otr-dev-request@lists.cypherpunks.ca</a>><br>
wrote:<br>
<br>
> Send OTR-dev mailing list submissions to<br>
> <a href="mailto:otr-dev@lists.cypherpunks.ca">otr-dev@lists.cypherpunks.ca</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="http://lists.cypherpunks.ca/mailman/listinfo/otr-dev" target="_blank">http://lists.cypherpunks.ca/mailman/listinfo/otr-dev</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:otr-dev-request@lists.cypherpunks.ca">otr-dev-request@lists.cypherpunks.ca</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:otr-dev-owner@lists.cypherpunks.ca">otr-dev-owner@lists.cypherpunks.ca</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of OTR-dev digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. OTR logo (Allan Nordh?y)<br>
> 2. Re: OTR logo (Hans-Christoph Steiner)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Tue, 5 May 2015 11:29:13 +0200<br>
> From: Allan Nordh?y <<a href="mailto:epost@anotheragency.no">epost@anotheragency.no</a>><br>
> To: <a href="mailto:otr-dev@lists.cypherpunks.ca">otr-dev@lists.cypherpunks.ca</a><br>
> Subject: [OTR-dev] OTR logo<br>
> Message-ID:<br>
> <CAMnoC=<br>
> <a href="mailto:zppASekMeCvcX%2B8xdVm5qxAiCPxB3XVhoCk-zGhzjahg@mail.gmail.com">zppASekMeCvcX+8xdVm5qxAiCPxB3XVhoCk-zGhzjahg@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> attached<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<br>
> <a href="http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20150505/95ec2a5e/attachment-0001.html" target="_blank">http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20150505/95ec2a5e/attachment-0001.html</a><br>
> ><br>
> -------------- next part --------------<br>
> A non-text attachment was scrubbed...<br>
> Name: otrlogo.png<br>
> Type: image/png<br>
> Size: 3912 bytes<br>
> Desc: not available<br>
> URL: <<br>
> <a href="http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20150505/95ec2a5e/attachment-0001.png" target="_blank">http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20150505/95ec2a5e/attachment-0001.png</a><br>
> ><br>
><br>
> ------------------------------<br>
><br>
> Message: 2<br>
> Date: Tue, 05 May 2015 10:20:12 -0400<br>
> From: Hans-Christoph Steiner <<a href="mailto:hans@guardianproject.info">hans@guardianproject.info</a>><br>
> To: <a href="mailto:otr-dev@lists.cypherpunks.ca">otr-dev@lists.cypherpunks.ca</a><br>
> Subject: Re: [OTR-dev] OTR logo<br>
> Message-ID: <<a href="mailto:5548D19C.8030500@guardianproject.info">5548D19C.8030500@guardianproject.info</a>><br>
> Content-Type: text/plain; charset=utf-8<br>
><br>
><br>
> interesting idea. Where did this logo come from?<br>
><br>
> .hc<br>
><br>
> Allan Nordh?y:<br>
> > attached<br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > OTR-dev mailing list<br>
> > <a href="mailto:OTR-dev@lists.cypherpunks.ca">OTR-dev@lists.cypherpunks.ca</a><br>
> > <a href="http://lists.cypherpunks.ca/mailman/listinfo/otr-dev" target="_blank">http://lists.cypherpunks.ca/mailman/listinfo/otr-dev</a><br>
> ><br>
><br>
> --<br>
> PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81<br>
> <a href="https://pgp.mit.edu/pks/lookup?op=vindex&search=0x9F0FE587374BBE81" target="_blank">https://pgp.mit.edu/pks/lookup?op=vindex&search=0x9F0FE587374BBE81</a><br>
><br>
><br>
> ------------------------------<br>
><br>
> _______________________________________________<br>
> OTR-dev mailing list<br>
> <a href="mailto:OTR-dev@lists.cypherpunks.ca">OTR-dev@lists.cypherpunks.ca</a><br>
> <a href="http://lists.cypherpunks.ca/mailman/listinfo/otr-dev" target="_blank">http://lists.cypherpunks.ca/mailman/listinfo/otr-dev</a><br>
><br>
><br>
> End of OTR-dev Digest, Vol 75, Issue 1<br>
> **************************************<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20150506/3f8ac69f/attachment-0001.html" target="_blank">http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20150506/3f8ac69f/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 05 May 2015 19:23:18 -0400<br>
From: Nick Guenther <<a href="mailto:nguenthe@uwaterloo.ca">nguenthe@uwaterloo.ca</a>><br>
To: <a href="mailto:otr-dev@lists.cypherpunks.ca">otr-dev@lists.cypherpunks.ca</a><br>
Subject: Re: [OTR-dev] OTR-dev Digest, Vol 75, Issue 1<br>
Message-ID: <<a href="mailto:554950E6.7020205@uwaterloo.ca">554950E6.7020205@uwaterloo.ca</a>><br>
Content-Type: text/plain; charset=windows-1252; format=flowed<br>
<br>
<br>
<br>
<br>
On 05/05/15 06:11 PM, Allan Nordh?y wrote:<br>
> It started with me being exposed to what Pidgin uses as an icon to signal<br>
> the nature of current OTR-connections.<br>
><br>
> At first some heads (?) forming a crowd of three for cleartext<br>
> conversations.<br>
> Changing into one person with a warning-sign before it for unverified<br>
> connections.<br>
> Verified connection are displayed as just a pictogram of one person.<br>
> For some reason this same icon changes and displays for IRC-chatrooms too,<br>
> still with the OTR-settings for the last opened one-to-one conversation.<br>
> [...]<br>
> Change the colours and you have all modes. Red for "not private", Yellow<br>
> for "unverified" and Green for "authenticated".<br>
><br>
> Or, still going with two different two designations; two megaphones, an<br>
> envelpe with a questionmark on it, and maybe an envelope being handed over.<br>
><br>
> Right now there are two instances of the same icon, one at the bottom next<br>
> to the chat-field and another up top along with "OTR" in writing, on a<br>
> different button to trigger the same menu.<br>
><br>
> What was initially a weekend job of drawing and digitizing resulted in good<br>
> feedback on one design, only to protract over a month, slowly but surely<br>
> passing my own judgement, steadily holding up against attempts to improve<br>
> it. Some pixel-fixes later and here we are.<br>
><br>
> The design I made is my own, so I can license it however you please.<br>
><br>
> -Allan Nordh?y (kingu)<br>
><br>
<br>
I think this is a great idea. Xabber(.apk)'s recent beta has added new<br>
logos next to the text input box (a good idea glibly ripped from<br>
Conversations.apk) and it is easily my favourite feature in the beta.<br>
It's aesthetically appealing which helps selling crypto to my friends,<br>
and it's also super readable and obvious what mode you're in.<br>
<br>
The Xabber icons are here for comparison:<br>
<a href="https://github.com/redsolution/xabber-android/commit/1ed13b2625d444112d85b3170c78903a11851fae" target="_blank">https://github.com/redsolution/xabber-android/commit/1ed13b2625d444112d85b3170c78903a11851fae</a><br>
<br>
-Nick Guenther<br>
Stats/CS, uwaterloo<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 6 May 2015 12:51:33 +0200<br>
From: Ian Goldberg <<a href="mailto:ian@cypherpunks.ca">ian@cypherpunks.ca</a>><br>
To: <a href="mailto:otr-dev@lists.cypherpunks.ca">otr-dev@lists.cypherpunks.ca</a><br>
Subject: Re: [OTR-dev] OTR-dev Digest, Vol 75, Issue 1<br>
Message-ID: <<a href="mailto:20150506105133.GO4766@yoink.cs.uwaterloo.ca">20150506105133.GO4766@yoink.cs.uwaterloo.ca</a>><br>
Content-Type: text/plain; charset=iso-8859-1<br>
<br>
On Wed, May 06, 2015 at 12:11:53AM +0200, Allan Nordh?y wrote:<br>
> Change the colours and you have all modes. Red for "not private", Yellow<br>
> for "unverified" and Green for "authenticated".<br>
<br>
Unfotunately, one can't use only a colour change to indicate something<br>
like this, for the sake of people who cannot see the colours. Having an<br>
OTR logo is great, and something we've indeed wanted for a while, and<br>
this is at the very least a good starting point; thanks! But I don't<br>
think we should use (coloured versions of) it for the security state<br>
indicators.<br>
<br>
Another logo idea previously proposed was some stylized form of "OTR" in<br>
a speech bubble; I suggested making it a dashed speech bubble (denoting<br>
whispering), but then I never heard back.<br>
<br>
- Ian<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 06 May 2015 13:49:13 +0100<br>
From: Peter Fairbrother <<a href="mailto:zenadsl6186@zen.co.uk">zenadsl6186@zen.co.uk</a>><br>
To: <a href="mailto:otr-dev@lists.cypherpunks.ca">otr-dev@lists.cypherpunks.ca</a><br>
Subject: Re: [OTR-dev] OTR-dev Digest, Vol 75, Issue 1<br>
Message-ID: <<a href="mailto:554A0DC9.2060709@zen.co.uk">554A0DC9.2060709@zen.co.uk</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
On 06/05/15 11:51, Ian Goldberg wrote:<br>
> On Wed, May 06, 2015 at 12:11:53AM +0200, Allan Nordh?y wrote:<br>
>> Change the colours and you have all modes. Red for "not private", Yellow<br>
>> for "unverified" and Green for "authenticated".<br>
><br>
> Unfortunately, one can't use only a colour change to indicate something<br>
> like this, for the sake of people who cannot see the colours.<br>
<br>
<br>
<br>
I'm not very familiar with OTR, but - a "not private" mode? And two<br>
other modes? Is that wise?<br>
<br>
Fifth Principle of Information Security Design: "Modes and choices are<br>
bad in crypto protocols, they give users choices which they are not<br>
qualified to make. It is your job to be clever, not the user's."<br>
<br>
Now OTR's clients are probably mostly a bit above the usual luser, but ..<br>
<br>
<br>
<br>
<br>
(Hi Ian, long time no see)<br>
<br>
<br>
-- Peter Fairbrother<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 6 May 2015 15:34:29 +0200<br>
From: Ian Goldberg <<a href="mailto:ian@cypherpunks.ca">ian@cypherpunks.ca</a>><br>
To: <a href="mailto:otr-dev@lists.cypherpunks.ca">otr-dev@lists.cypherpunks.ca</a><br>
Subject: Re: [OTR-dev] OTR-dev Digest, Vol 75, Issue 1<br>
Message-ID: <<a href="mailto:20150506133429.GT4766@yoink.cs.uwaterloo.ca">20150506133429.GT4766@yoink.cs.uwaterloo.ca</a>><br>
Content-Type: text/plain; charset=iso-8859-1<br>
<br>
On Wed, May 06, 2015 at 01:49:13PM +0100, Peter Fairbrother wrote:<br>
> On 06/05/15 11:51, Ian Goldberg wrote:<br>
> >On Wed, May 06, 2015 at 12:11:53AM +0200, Allan Nordh?y wrote:<br>
> >>Change the colours and you have all modes. Red for "not private", Yellow<br>
> >>for "unverified" and Green for "authenticated".<br>
> ><br>
> >Unfortunately, one can't use only a colour change to indicate something<br>
> >like this, for the sake of people who cannot see the colours.<br>
><br>
><br>
><br>
> I'm not very familiar with OTR, but - a "not private" mode? And two<br>
> other modes? Is that wise?<br>
><br>
> Fifth Principle of Information Security Design: "Modes and choices<br>
> are bad in crypto protocols, they give users choices which they are<br>
> not qualified to make. It is your job to be clever, not the user's."<br>
><br>
> Now OTR's clients are probably mostly a bit above the usual luser, but ..<br>
<br>
Yes, totally agree. For many OTR users, who might be using it<br>
unintentionally because their IM client just ships with it by default,<br>
say, OTR will just protect their conversations against passive<br>
eavesdroppers without them needing to know anything.<br>
<br>
The mode indicators (at least "Not Private") come in because we're not<br>
providing a secure messaging network ab initio. Instead, you're talking<br>
to your existing contacts, who may or may not be equipped to encrypt<br>
your conversation. So while it is of course best to make a system that<br>
*cannot* send unencrypted messages, there are compromises one needs to<br>
make when deploying a security/privacy layer on top of an existing<br>
system. (Which is why you should design security and privacy *into* the<br>
system, and not bolt it on top. But we didn't get to design AIM, ICQ,<br>
or XMPP.)<br>
<br>
- Ian<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
OTR-dev mailing list<br>
<a href="mailto:OTR-dev@lists.cypherpunks.ca">OTR-dev@lists.cypherpunks.ca</a><br>
<a href="http://lists.cypherpunks.ca/mailman/listinfo/otr-dev" target="_blank">http://lists.cypherpunks.ca/mailman/listinfo/otr-dev</a><br>
<br>
<br>
End of OTR-dev Digest, Vol 75, Issue 2<br>
**************************************<br>
</blockquote></div><br></div></div>