Two new data types: `DbusMention` (created by @0b11001111) and `DbusAttachment`.
Two new signals, `MessageReceivedV2` and `SyncMessageReceivedV2`.
This is to address #671#316#658 and #491, in particular addressing the issues raised by @AsamK in #658.
The new signals provide the new data structures to the user program, while the existing signals, `MessageReceived` and `SyncMessageReceived`, continue to provide the old data types (with no information about mentions or attachment metadata).
As a result, for each message received, two signals will be emitted: the legacy signal and the V2 signal. Existing (old-style) programs will not see the V2 signal, and so nothing will break. New programs can ignore the legacy signal and process the enhanced data.
For daemon command all local users will be exposed as dbus objects
If only one local user exists, all other commands will use that user,
otherwise a user has to be specified.
* Added json output to listGroups and allowed json to be activated with -j
* Renamed classes
* Added AsamK's suggestions
* Removed isRegisted check since that is causing a conflict with upstream
* Fixed an issue in the help message for listGroupsCommand
* Re-enabled --json for receive and getUserStatuses commands as deprecated
* Added better depricated warning message and clarified some java doc stuff
Since version 0.6.8 signal-cli uses hypfvieh dbus-java, so installing the packages libunixsocket-java (Debian), libmatthew-java (Fedora) or libmatthew-unix-java (ArchLinux) is not necessary.
* Add blockContact and unblockContact subcommands
* Send blocked status in contacts sync
* Use only one method for blocking and unblocking
* Add blocking/unblocking for groups
* Prevent blocked messages from being printed
* Print blocked property in listContacts and listGroups commands
* Handle BlockedListMessages
* Store blocked state from incoming contact and group sync messages
* Minor changes and corrections
* Add block and unblock commands to man file (and also fix some headings of commands)
As Signal Desktop does not allow its users to update the contact names,
it would be nice to be able to update contact names from signal-cli when
the latter is the master device.
The command `setContactName` allow to set the name for the given contact
in the local store. `sendContacts` can then be used to push the updated
contact list on Signal servers.
Closes#228
Two new commands are added `setProfileName` and `setProfileAvatar` which
allow to update the name and avatar visible by other users for the
current profiles.
Closes#227
