Dino

There has been some physical damage to our server after a power outage in the data center, combined with an unexpected UPS failure. For that reason, the dino.im website and chat room are currently offline. We're working on getting everything back up, but recovery will take several days.

Dino 0.5 is out! 🥳

Dino now features improved file transfers and two completely reworked dialogs.

Release blog post: https://dino.im/blog/2025/04/dino-0.5-release/

#dino #xmpp #gtk #gnome

Dino 0.4 is released! 🎊️

Dino now supports message reactions and replies. Furthermore, we switched to GTK4 and libadwaita. #dino #xmpp

Release blog post: https://dino.im/blog/2023/02/dino-0.4-release/

Dino 0.3 is released and supports video calls and conferences! 🥳

You can call a friend or a group of people. Calls are e2e-encrypted, peer-to-peer and compatible with other XMPP applications.

Release blog post: https://dino.im/blog/2022/02/dino-0.3-release/

Video calls in Dino are slowly coming together. We are already making successful OMEMO encrypted video calls! The feature is included in our nightly builds now, but there's still further work to be done. #dino #xmpp

Dino 0.2 is out!

Dino is a privacy-friendly messaging application. The 0.2 release adds message correction, improves the file upload functionality and provides more information on encryption.

Release blog post: https://dino.im/blog/2020/11/dino-0.2-release/

@NGIZero@mastodon.xyz will support our upcoming work on calls and video-conferences in Dino. Read our announcement post: https://dino.im/blog/2020/08/setting-out-for-calls-and-conferences/ #dino #xmpp

During this year's Google Summer of Code, Anmol will implement optional real-time texting in Dino. Real-time text means that text is transmitted and displayed to the receiver while it is being typed. Anmol will write about his progress here: https://wolfieanmol.github.io/gsoc-blog/ #Dino #XMPP #GSoC

Dino 0.1 is released! 🎉

Dino is a secure and open-source application for decentralized messaging. It uses the XMPP (“Jabber”) protocol and is interoperable with other XMPP clients and servers. We aim to provide an intuitive, clean and modern user interface.

Release blog post: https://dino.im/blog/2020/01/dino-0.1-release/

We have this awesome lighted acrylic glass Dino at the XMPP assembly at 36c3. Come over! You can set the colors of the LEDs via a message to xmpp:color@dino.im. #Dino #XMPP #36c3

Dino's app menu now contains a "Keyboard Shortcuts" list and an "About Dino" dialog that displays the app version and other meta info. The current git master has the version 0.0~git594.20191218.9fe84505. Upcoming: Version 0.1. #Dino #XMPP

Multi-user chats are often divided into two use cases: Groups and Channels. In Groups you talk with specific people about varying topics, while in Channels you talk with a changing set of people about a specific topic.
Dino displays a list of member names as the default Group name and uses member avatars to generate a default Group avatar. Both features wouldn't make sense in a Channel with a continuously changing set of members. #Dino #XMPP

Testing an upcoming feature during the #Stockholm XMPP sprint: Leave a group chat on #Dino and #Conversations will leave as well, join a new group chat on Conversations and Dino will join too. The underlying protocol extension was also implemented by #Gajim and #prosody during the sprint. #XMPP

With recent changes Dino can now transfer files via an OMEMO encrypted Jingle stream (XEP-0391). This enables the encrypted peer-to-peer exchange of large files with other supporting clients. Conversations also supports this in its latest release. #Dino #XMPP

An emoji picker is now reachable via a button located next to the message input field. GTK also offers the shortcut CTRL+. to open an emoji picker. #Dino #XMPP

Support for #Jingle file transfer over #SOCKS5 was merged into #Dino. SOCKS5 enables data transfer without an intermediary but also supports transfer via a server if a #firewall prohibits direct transfer. Data transfer over the #XMPP stream ("In-Band-Bytestream") has an overhead due to encoding, but serves as a fallback if http file upload and SOCKS5 fail.