News for hackers. Stuff that matters.
Re:Dino: Jabber/XMPP Client Using GTK+/Vala by torrance on Saturday April 28, 2018 @04:35PM (#16949291)
Thank you for writing this with such a pleasant an UI and written in a _native_ widget toolkit.
Re:Dino: Jabber/XMPP Client Using GTK+/Vala by joecool1029 on Saturday April 28, 2018 @03:24PM (#16949068)
Weird that they included openpgp and omemo as encryption methods but left out the much more popular OTR system for XMPP.

I get that OMEMO is the future but very few clients support it currently, and as I understand even less servers support the features required to support it.

Oh and OpenPGP just sucks for instant messaging. (long-lived key with no forward secrecy)

Re:Dino: Jabber/XMPP Client Using GTK+/Vala by diaz on Saturday April 28, 2018 @07:31PM (#16949973)
OTR is a dead end. Pgp for people who want to use it and omemo for everyone by default is the way to go. Latest release of Conversations also removed OTR. It's not needed. Having more than one option is already confusing enough. Having 3 is just crazy. What was blocking omemo implementation was problems related to libraries not being available before with licenses that made sense. That seems solved now.
Re:Dino: Jabber/XMPP Client Using GTK+/Vala by upofadown on Saturday April 28, 2018 @08:44PM (#16950195)
OMEMO adoption seems to be on a roll:

* https://omemo.top/

> even less servers support the features required to support it.

Does the server require something special to support OMEMO?

Re:Dino: Jabber/XMPP Client Using GTK+/Vala by upofadown on Thursday May 03, 2018 @08:53AM (#16985487)
To answer my own question, OMEMO requires the server to support "XEP-0163: Personal Eventing Protocol". XEP-0163 seems to be more or less supported everywhere. It is sort of amusing that it was originally intended for stuff like letting your contacts know what song you are listening too. Now that it is an OMEMO requirement it has for all practical purposes become mandatory.
Re:Dino: Jabber/XMPP Client Using GTK+/Vala by joecool1029 on Monday May 07, 2018 @12:23PM (#17014002)
Well, not everywhere. But a good number with some notable services left out. Here's a chart: https://conversations.im/compliance/
Re:Dino: Jabber/XMPP Client Using GTK+/Vala by spystath on Sunday April 29, 2018 @08:02AM (#16951671)
You will probably need at least Message Carbons (XEP-0280)[0] to synchronise your devices and maybe Message Archives (XEP-0313)[1] to have some kind of history available to them. However this not really tied to OMEMO itself, it's just to provide what's expected of a modern IM experience. I think all servers support them nowadays, anyway.

[0] https://xmpp.org/extensions/xep-0280.html

[1] https://xmpp.org/extensions/xep-0313.html

Re:Dino: Jabber/XMPP Client Using GTK+/Vala by tcit on Saturday April 28, 2018 @03:30PM (#16949095)
I guess OMEMO was their priority at the time, and PGP was quite easy to handle.
Re:Dino: Jabber/XMPP Client Using GTK+/Vala by xorcist on Saturday April 28, 2018 @03:32PM (#16949100)
If you are looking for that feature set in a mature product, check out Gajim.
Re:Dino: Jabber/XMPP Client Using GTK+/Vala by Boulth on Sunday April 29, 2018 @08:00AM (#16951666)
Gajim is also far more complex and a little bit buggy. I'm using it daily and it pains me that even removing contacts throws an exception. Unfortunately dino on the other hand looks like it's stuch in a forever alpha state.
Re:Dino: Jabber/XMPP Client Using GTK+/Vala by camgunz on Saturday April 28, 2018 @05:08PM (#16949421)
This looks great, and it's in Vala! Nice :)