Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
Stop automagically select default encryption
Selecting a default encryption (in our case OMEMO) has several down sides. First of all users might have perfectly valid reasons not to use encryption at all such as using the same private server. Second of all the way it was implemented Conversations would automatically fall back to plain text as soon as the conditions changed (recipient switches to device with no encryption) which lead to unexpected situations. Thirdly having a default encryptions speaks against the 'mission statement' of Conversations of not forcing its security and privacey aspects upon the user. And last but not least the goal of implementing this feature in the first place: Be encrypted by default didn't work at all. I don't think there was a single user that we succesfully 'tricked' into using OMEMO who otherwise wouldn't have used it.
- Loading branch information
035d0c7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏
035d0c7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't do this. This is a huge mistake.
035d0c7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Explain?!
035d0c7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And so it was that governments and blackhats alike rejoiced on that day.