{"action":"created","issue":{"url":"https://api.github.com/repos/siacs/Conversations/issues/1501","labels_url":"https://api.github.com/repos/siacs/Conversations/issues/1501/labels{/name}","comments_url":"https://api.github.com/repos/siacs/Conversations/issues/1501/comments","events_url":"https://api.github.com/repos/siacs/Conversations/issues/1501/events","html_url":"https://github.com/siacs/Conversations/issues/1501","id":111773656,"number":1501,"title":"synchronize encryption protocols","user":{"login":"aeuii","id":12943195,"avatar_url":"https://avatars.githubusercontent.com/u/12943195?v=3","gravatar_id":"","url":"https://api.github.com/users/aeuii","html_url":"https://github.com/aeuii","followers_url":"https://api.github.com/users/aeuii/followers","following_url":"https://api.github.com/users/aeuii/following{/other_user}","gists_url":"https://api.github.com/users/aeuii/gists{/gist_id}","starred_url":"https://api.github.com/users/aeuii/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aeuii/subscriptions","organizations_url":"https://api.github.com/users/aeuii/orgs","repos_url":"https://api.github.com/users/aeuii/repos","events_url":"https://api.github.com/users/aeuii/events{/privacy}","received_events_url":"https://api.github.com/users/aeuii/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-10-16T07:04:19Z","updated_at":"2015-10-16T16:33:12Z","closed_at":null,"body":"At the moment, it is possible that two users of Conversations choose two different encryption methods, e.g. user A selects OTR and user B selects OMEMO.\r\n\r\nI think this should not happen and Conversations should prevent such situation. My suggestion is that when a user A selects OTR, it should be noticed by the Conversations of B and start talking OTR too. As soon as B decides to change to OMEMO, the client of A should notice that too and switch seamlessly to OMEMO. Such behavior seem more intuitive and less obtrusive (as I understand, one of the main goals of Conversations). Is there any disadvantage of that?\r\n\r\n(Currently agreement or disagreement in protocol selection is indicated by green and red background. It is a poor UI, because it is not clear and confusing for new and old users. Not clear -- especially for new users -- because it could equally be just a colorful theme and there's no indication that the colors have any meaning. Confusing -- because people aware of encryption intuitively associate the colors with encrypted/unencrypted status of the message, which is wrong.)"},"comment":{"url":"https://api.github.com/repos/siacs/Conversations/issues/comments/148762619","html_url":"https://github.com/siacs/Conversations/issues/1501#issuecomment-148762619","issue_url":"https://api.github.com/repos/siacs/Conversations/issues/1501","id":148762619,"user":{"login":"SamWhited","id":512573,"avatar_url":"https://avatars.githubusercontent.com/u/512573?v=3","gravatar_id":"","url":"https://api.github.com/users/SamWhited","html_url":"https://github.com/SamWhited","followers_url":"https://api.github.com/users/SamWhited/followers","following_url":"https://api.github.com/users/SamWhited/following{/other_user}","gists_url":"https://api.github.com/users/SamWhited/gists{/gist_id}","starred_url":"https://api.github.com/users/SamWhited/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SamWhited/subscriptions","organizations_url":"https://api.github.com/users/SamWhited/orgs","repos_url":"https://api.github.com/users/SamWhited/repos","events_url":"https://api.github.com/users/SamWhited/events{/privacy}","received_events_url":"https://api.github.com/users/SamWhited/received_events","type":"User","site_admin":false},"created_at":"2015-10-16T16:33:12Z","updated_at":"2015-10-16T16:33:12Z","body":"> I think about a situation, where one party turn on the encryption the other client starts to respond with the same protocol.\r\n\r\nLike @iNPUTmice said, this isn't actually a good thing. I might not want to turn encryption on (eg. if one of my mechanisms is signed-PGP [not actually supported by Conversations, but it's just an example] a remote user could trick me into sending messages with absolutely no form of plausable deniability). Alternatively, if I'm using OMEMO and a user switches, suddenly I could be using a known-broken version of some other encryption protocol, or they could turn encryption off altogether and I might not notice.\r\n\r\nThings like this should NEVER be done automatically without the users consent."}}