libgnunetchat 0.1.0 released
We are pleased to announce the release of the client side library libgnunetchat 0.1.0.
This library brings an abstraction layer using the client API from different GNUnet services to provide the functionality of a typical messenger application. The goal is to make developing such applications easier and independent of the GUI toolkit. So people can develop different interfaces being compatible with eachother despite visual differences, a few missing features or differences in overall design.
The library relies on multiple services from GNUnet to implement its features. More information about that can be found here.
The GPG key used to sign is: 3D11063C10F98D14BD24D1470B0998EF86F59B6A
Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try http://ftp.gnu.org/gnu/gnunet/
Noteworthy changes in 0.1.0
- This release requires the GNUnet Messenger Service 0.1!
- It allows account management (creation, listing and deletion).
- Clients are able to switch between accounts during runtime.
- The client can rename an account or update its key.
- Contact exchange is possible via lobbies in form of URIs to be shared as text form or potentially QR encoded.
- Each resource allows handling a user pointer for the client application.
- Contacts and groups can be managed individually and given a custom nick name.
- It is possible to request and open a direct chat with any contact.
- Groups allow listing their members with custom user pointers related to the group memberships.
- Chats can be left explicitly.
- Each chat will be represented as context resource abstracting the variant of chat.
- It is possible to send text messages, send files, share files and send read receipts explicitly.
- Received messages allow checking for a read receipt status.
- Messages can be deleted with a custom delay.
- Files in a chat can be fully managed (they can be uploaded, downloaded, unindexed and provide a decrypted temporary preview if necessary) while being encrypted individually.
- The status of each operation (upload, download, unindex) regarding files can be tracked.
- Received invitations to new chats can be accepted.
A detailed list of changes can be found in the ChangeLog.
- The test cases are not fully complete and they may fail because of timeouts erratically.
In addition to this list, you may also want to consult our bug tracker at bugs.gnunet.org.