Answer by Mikaela for [feature-request] XMPP OTR support in messages
I opened the separate thread on OMEMO here: https://together.jolla.com/question/133414/feature-request-omemo-support/ I know I probably shouldn't make this an answer, but I cannot make any sense of the...
View ArticleComment by null
"I don't understand how to use OTR, so that must mean it's broken and therefore no one is allowed to request it, since it'd prove me wrong if other people were actually able to use it and we can't have...
View ArticleComment by nthn
If you aren't using either of those clients, you're using one with an OTR implementation full of bugs. Not only do you insist on using a broken protocol, you insist on a broken implementation of it as...
View ArticleComment by null
Also, claiming to know best what the other 300 people want is the top of your arrogance.
View ArticleComment by null
OTR works and has been working for years. OMEMO is supported by two clients I don't and won't use and no one I know uses. That's entirely besides the point though. Even if OMEMO was the absolute...
View ArticleComment by nthn
@null: Of the 300 people who voted for it, I would guess 298 don't care what the name of the encryption protocol is, as long as it works. OMEMO does, and can. OTR doesn't, can't, and won't. I will...
View ArticleComment by null
And I still say, if you want a feature implemented, stop overtaking other feature requests and make your own. Well, I downvoted and unfollowed your stolen request. Too lazy for an editwar over a...
View ArticleComment by nthn
As a follow up, the 'planned' desktop implementation is already here: https://github.com/omemo/gajim-omemo
View ArticleComment by nthn
@MartinK: but it never gets sent in plain text. It's sent encrypted to all of your devices that support OMEMO and whose keys you have trusted, any other devices don't receive anything at all. Again, if...
View ArticleComment by MartinK
@nthn: I just mean it should only be readable on the device you are on by default until you clear additional devices. And this should preferably be per contact, as there might be some conversations...
View ArticleComment by nthn
@ExTechOp: saying that it's available for multiple clients/platforms is meaningless when you consider that in most clients, the plugin implementing OTR support hasn't been updated in years and probably...
View ArticleComment by MartinK
@hobarrera: What you see as technical limitations I see as a potential security vulnerability - at least if the decryptable OMEMO messages would be sent to all users connected devices without explicit...
View ArticleComment by ExTechOp
@nthn Desktop implementation of OMEMO is *planned* vs. OTR which is currently available for diverse platforms and protocols (like irc). The best-laid schemes o' mice an' men Gang aft agley, An' lea'e...
View ArticleComment by nthn
@ExTechOp: for one, Jolla has nothing to do with this. It needs to be implemented in Telepathy, once it's available there it can work in Sailfish instantly (probably some UI would be needed, of...
View ArticleComment by ExTechOp
The following is not meant as a personal comment to you, but as general observations on the development of different internet chat protocols and client/server software. I've seen several very promising...
View ArticleComment by nthn
I just meant to say that OTR is completely and utterly deprecated by OMEMO, everything OTR does is done better by OMEMO, so there is no point in supporting it anymore (and judging by the extreme lack...
View ArticleComment by null
I'm not trolling, I just don't have the problems you're describing. In any case, this question is about OTR support, if you want another encryption technology I'd suggest starting a new topic.
View ArticleComment by WhyNotHugo
People stop trolling like this. Telling people not to switch devices, or to alter how they work isn't how you deal with technical limitations. You adapt software to people's needs, not the other way...
View Article