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 ArticleComment by null
So just read the last message again before you switch to the other device, if you're having trouble remembering what you're currently talking about.
View ArticleComment by WhyNotHugo
The problem with starting a new session is that: you're starting a new session. You can't read messages delivered on the previous session to the other device, for one, and once you switch back to that...
View ArticleComment by null
No, why would I constantly switch devices? And if I would, what's the problem with starting a new session?
View ArticleComment by WhyNotHugo
> Never had a problem with sessions, a properly configured client starts them automatically. Then you probably don't switch across clients constantly during a conversation. Or took *a lot* of effort...
View ArticleComment by null
Never had a problem with sessions, a properly configured client starts them automatically. And why would I want to read the messages on all my devices? It kind of defeats the purpose of end-to-end...
View ArticleComment by nthn
@null: it never worked properly. Having to start/end sessions every time you want to talk to someone is a royal pain. Your messages are only encrypted to one of your recipient's devices - good luck...
View ArticleComment by nthn
I think given the fact that OMEMO is already lightyears ahead of OTR in terms of actually working, I can safely say OTR is the one with a long way to go. Or actually, a very short one - death.
View ArticleAnswer by nthn for [feature-request] XMPP OTR support in messages
OMEMO now exists, by definition it's already a lot better than OTR because you can use it with multiple devices and it doesn't have problems with beginning/ending sessions either. 'Only' needs to be...
View ArticleComment by ExTechOp
No progress here for more than three years. Is there any hope this will get done?
View ArticleComment by dsilveira
I use archlinux, so I just got the recent update with the features shown in the linked blog post. If you use a different distro, you'll probably need to wait for the next version of your distro...
View ArticleComment by cvp
nice. can you explain how do you do that? Hope jolla will work on it now (otr, (video)call, groupchat) and may be file transfer.
View ArticleComment by WhyNotHugo
I'm wondering if, for the time being, there's some way to enable it by editing telepathy's settings via some other interface.
View ArticleAnswer by dsilveira for [feature-request] XMPP OTR support in messages
**Great news** KDE Telepathy, [has already implemented the required GUI glue to reveal Telepathy's OTR 3 support](http://blog.davidedmundson.co.uk/blog/ktp_0.9). Now it's totally up to Jolla to put the...
View ArticleComment by Eierkopp
Basically it's already obsolete since OTR is now merged into mainline telepathy. Anyway the autogen.sh/configure script will tell you, which software needs to be upgraded to compile telepathy-gabble. I...
View ArticleComment by nthn
@Eierkopp: can you explain what exactly you did to make OTR work? I'd like to give it a try myself (and maybe other people want to try as well).
View ArticleComment by Eierkopp
I just compiled Xavier Claessens OTR stuff from the otr branch of git://git.collabora.co.uk/git/user/xclaesse/telepathy-gabble.git. It requires updates to quite a lot of basic libraries like...
View ArticleComment by kat6
@tad That is really cool! Thanks for the link. I hadn't even heard about it. I hope telepathy implements it, so we can have it too.
View ArticleComment by tad
@kat6 IMO everything should be focussed on [OMEMO](https://together.jolla.com/question/133414/feature-request-omemo-support/) as OTR is not adequate for mobile use
View ArticleComment by tomka
Yeah, please add the the minimal UI glue. Or point us to the source so that we could come up with something on our own. This is really important for many users.
View ArticleComment by Vlad
i don't want to complain about this but, this is an feature which is very important for a lot of people and an seeling point to. You also update something like facebook when they change there api,...
View ArticleComment by hasdf
Still waiting for "just require minimal UI glue from our side"! Come on, it's a really important feature.
View ArticleComment by Vlad
are there any news about otr out of the box on sailfish os? this function is the only i realy miss on sfos so far :(
View ArticleComment by encrypteddragon
I'm starting to think that OTR is being forgotten, can someone please give a fresh Update? I'm quite keep on privacy and with the resent reveal of more "broken" protocols and the porrf that PGP and OTR...
View ArticleComment by WhyNotHugo
Facebook announced some time ago that they'll be dropping XMPP anyway, so don't get your hopes up too much. Better to start thinking about a read (and federated) XMPP server.
View ArticleComment by WhyNotHugo
"The Chat/XMPP service and API, located at chat.facebook.com, will not be available once 1.0 is deprecated.": https://developers.facebook.com/docs/apps/changelog
View ArticleComment by nthn
Unfortunately it seems like not much has happened for the last few months, unless discussion and development is now being done somewhere else: https://bugs.freedesktop.org/show_bug.cgi?id=16891#c92
View ArticleComment by dsilveira
Facebook? I knew about gogle. What are they dropping it in favor of? I don't think that should be a big problem, just as long as the protocol is open, then telepathy can implement it
View Article
