Elementi taggati con: dino
What is Dino?
Dino is a modern IM client using XMPP (Jabber) with support for both OpenPGP and OMEMO. It looks very nice and can already be used for chatting and group conversations. It is, however, not yet stable nor feature-complete. If you are looking for something like Conversations (Android XMPP client), but for the desktop, Dino is for you. If you like to have something more stable and feature-complete, try Gajim instead. I use both! :~)
Dino is written in C and Vala, uses the GTK+ UI toolkit and looks best in Gnome, XFCE, or other GTK+ based desktops. I heard about planned versions for Windows and MacOS, too, but don't hold your breath.
How to install Dino on Debian?
Since yesterday, the Dino IM client is available in the official Debian repositories, but so far only in the "experimental" distribution. To install it, Debian users have to:
$ echo deb https://deb.debian.org/debian/ experimental main | sudo tee /etc/apt/sources.list.d/experimental.list
$ sudo apt update
$ sudo apt -t experimental install dino-im
This should work on nine official and five unofficial architectures for at least unstable and testing. Not sure about stable. I'm pretty sure, that oldstable will not work.
Why the "-im" suffix for Dino in Debian?
There used to be another program, an "integrated MIDI piano roll editor and sequencer engine", by the same name in Debian. Many references to the old program still exist, so it would be problematic to recycle the name for a different purpose.
#xmpp #debian #dino #jabber #openpgp #omemo #im #federation #chat
Install Dino on Debian-based Systems
If you run Debian testing or unstable, you may install dino-im directly from Debian experimental. Easy.
If you run Debian stable, or Ubuntu, or Mint etc. there are some more steps involved. Make sure, your system has GTK3 version 3.22 at least. This is required by Dino. E.g. for Ubuntu this means 17.04 or newer. Also, you may need to install some development tools and libraries. During the build, you'll see which one are missing on your system. I did not try this myself, this is just what I hope should work - quick and dirty:
- $ dget http://httpredir.debian.org/debian/pool/main/libs/libsignal-protocol-c/libsignal-protocol-c_2.3.1+git20171007-1.dsc
- cd libsignal-protocol-c-2.3.1+git20171007/
- sudo apt install check cmake debhelper dpkg-dev libssl-dev protobuf-c-compiler
- $ dpkg-buildpackage -rfakeroot -uc -us
- cd ..
- sudo dpkg -i libsignal-protocol-c2_2.3.1+git20171007-1_amd64.deb libsignal-protocol-c-dev_2.3.1+git20171007-1_amd64.deb
- dget http://httpredir.debian.org/debian/pool/main/d/dino-im/dino-im_0.0.git20171101-1.dsc
- cd dino-im-0.0.git20171101/
- sudo apt install dh-exec gettext libgcrypt20-dev libgee-0.8-dev libglib2.0-dev libgpgme-dev libgtk-3-dev libnotify-dev libsoup2.4-dev libsqlite3-dev ninja-build valac
- $ dpkg-buildpackage -rfakeroot -uc -us
- cd ..
- sudo dpkg -i dino-im_0.0.git20171101-1_amd64.deb dino-im-common_0.0.git20171101-1_all.deb
#debian #ubuntu #mint #dino #xmpp
Daniel Gultsch, developer of Android XMPP client Conversations, writes,
#xmpp #omemo #conversations #psi #gajim #zom #chatsecure #dino #jsxc #federation #encryption
Why it took us more than two years to enable End-to-End encryption by default: The first in a series of essays leading up to the release of Conversations 2.0
The other big hurdle we had to overcome was the adoption rate in clients. If you send OMEMO encrypted messages by default you should have a reasonable expectation that your contact will be able to decrypt the message. Reasonable expectation doesn’t mean that every single client out there has to support it—In an ecosystem with hundreds of small, badly maintained clients that’s just not feasible—but the major clients should at least have a plugin available.
In March 2018 we finally reached the point where every plattform has one or more clients with OMEMO support. Conversations and Zom on Android, ChatSecure on iOS, Psi and Gajim on the desktop. The up and coming desktop client Dino—despite not having had an initial release—already has support for OMEMO as well. And even the webclient JSXC has a plugin available.
Considering the complexity of OMEMO and the fact that most of these clients are developed by people in their spare time, this is actually quite an impressive adoption rate.
Moxie Marlinspike, in his 2016 propaganda piece ignorantly bashing XMPP, had one valid point: Enabling end-to-end encryption in a homogenous environment is easier than introducing it in a heterogenous one like Jabber. Nobody is denying that. However, if something is hard to achieve there are two possible approaches: Either try your best and don’t give up, or put your head in the sand and create yet another walled garden that is no different from other proprietary solutions.
Admittedly it has taken us a while to get to a point where we can enable end-to-end encryption by default, but it was worth the effort in that we ended up with something that is different from WhatsApp in more than just marketing.