In November we worked on Chat Markers, a feature many of you had wished to see in Gajim. Chat Markers enable you to see whether your contact has read your messages, and they help Gajim to manage notifications if you read messages on your phone or other devices.
Changes in Gajim
A long anticipated feature has finally found its way to Gajim: Chat Markers (XEP-0333). You already know the check mark which Gajim shows as soon as a message has been delivered (XEP-0184). Now, as soon as your contact reads your message, you’ll notice a double check mark replacing the single check mark, marking the message as ‘read’. This is of course on the condition that your contact’s chat client actually sends Chat Markers. Gajim lets you choose whether you want to send these markers via Account Settings > Privacy > Send Read Markers. As soon as you read a message on another device (e.g. your phone), Gajim will remove the now obsolete notification. By default, this works for 1:1 chats and private group chats (tested with Conversations and Dino).
What else happened
- Added fail-safe for starting
Gajim.exedirectly while in Portable mode
- Added a new Bruno-themed Status Icon Set
- Implemented improvements for Dataforms (e.g. for AdHoc Commands)
- Fixed a bug which occured on some servers while sending a file via HTTP File Upload (#10337)
- Fixed a performance issue when running Gajim together with media players (#10339)
This month, Gajim’s OpenPGP plugin received an update implementing a backend for GPGME (GnuPG Made Easy). Furthermore, the OMEMO plugin has been prepared to be able to send
markable stanzas in order to support Chat Markers.
Changes in python-nbxmpp
After finishing the implementation of Tasks, improvements for OpenPGP and AdHoc Commands have been added.
As always, feel free to join email@example.com to discuss with us.