A new version of Delta Chat 1.22 has been released - a messenger that uses email as a transport instead of its own servers (chat-over-email, a specialized mail client that works like a messenger). The application code is distributed under the GPLv3 license, and the core library is available under the MPL 2.0 (Mozilla Public License). The release is available on Google Play and F-Droid. A similar desktop version is being delayed.
In the new version:
- Significantly improved the process of interacting with people who are not in the address book. If a person not listed in the address book sends a message to the user or adds them to a group, the specified user is now sent a Chat Request to accept or decline further communication. The request may include elements of regular messages (attachments, pictures) and is displayed directly in the chat list, but is provided with a special label. If accepted, the request is transformed into a separate chat. To return to correspondence, the request can be pinned in a conspicuous place or moved to the archive.
- The implementation of support for multiple Delta Chat (Multi-Account) accounts in one application has been transferred to a new handler unified for all platforms, which provides the ability to parallelize work with accounts (switching between accounts is now instantaneous). The handler also allows you to perform group join operations in the background. In addition to builds for Android and desktop systems, the ability to use multiple accounts is also implemented in the version for the iOS platform.
- The top panel provides a connection status display that allows you to quickly assess the lack of communication due to network problems. When you click on the title, a dialog appears with more detailed information about the reasons for the lack of connection, for example, the traffic quota data transmitted by the provider is shown.
Recall that Delta Chat does not use its own servers and can work through almost any mail server that supports SMTP and IMAP (Push-IMAP is used to quickly determine when new messages arrive). Encryption is supported using OpenPGP and the Autocrypt standard for easy automatic configuration and key exchange without the use of key servers (the key is automatically transmitted in the first message sent). The end-to-end encryption implementation is based on the rPGP code, which passed an independent security audit this year. Traffic is encrypted using TLS in the implementation of standard system libraries.
Delta Chat is completely controlled by the user and is not tied to centralized services. It does not require registration in new services to work - you can use an existing email as an identifier. If the correspondent does not use Delta Chat, he can read the message as a regular letter. The fight against spam is carried out by screening messages from unknown users (by default, only messages from users from the address book and those to whom messages were sent before, as well as replies to own messages, are displayed). It is possible to display attachments and attached images and videos.
It supports the creation of group chats in which several participants can communicate. At the same time, it is possible to bind a verified list of participants to the group, which does not allow unauthorized persons to read messages (members are verified using a cryptographic signature, and messages are encrypted using end-to-end encryption). Connection to verified groups is carried out by sending an invitation with a QR code.
The core of the messenger is developed separately in the form of a library and can be used to write new clients and bots. The current version of the core library is written in Rust (the old version was written in C). There are bindings for Python, Node.js and Java. Unofficial bindings for Go are in development. There is a DeltaChat for libpurple that can use both the new Rust core and the old C core.
Source: opennet.ru