ChangeLog


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

## Version 0.3.1
* Makes dependency to libcheck optional (only required for building test cases)
* Fixes file iteration of chat context
* Fixes some build issues

## Version 0.3.0
* This release requires the GNUnet Messenger Service 0.3!
* It allows ticket management for tickets sent from contacts.
* Deletions or other updates of messages result in separate event calls.
* It is possible to tag messages or contacts.
* Invitations can be rejected via tag messages.
* Contacts can be blocked or unblocked which results in filtering messages.
* Processing of messages is ensured by enforcing logical order of callbacks while querying old messages.
* Private messages are readable to its sender.
* Messages provide information about its recipient.
* Logouts get processed on application level on exit.
* Delays message callbacks depending on message kind (deletion with custom delay).
* New debug tools are available to visualize the message graph.
* Add test case for message receivement.
* Multiple issues are fixed.

## Version 0.1.3
* Use Meson as build system instead of GNU Automake
* Fix issues regarding inclusion of private headers

## Version 0.1.2
* Improve GNU Automake configuration
* Update API usage regarding changes in GNUnet 0.19.0

## Version 0.1.1
* Fixes typos, memory leaks and other reliability issues
* Transitions from single Makefile to GNU Automake
* Updates API usage regarding changes in GNUnet 0.18.0

## Version 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.