commit e77a0e798c2a63ba6ccf7756eb294be54bfbb553
parent 13a98368bf21a3fd7eb0ab1a95ace7875ae45004
Author: Jacki <jacki@thejackimonster.de>
Date: Mon, 26 Feb 2024 16:23:38 +0100
messenger: add missing kinds of messages
Signed-off-by: Jacki <jacki@thejackimonster.de>
Diffstat:
1 file changed, 54 insertions(+), 0 deletions(-)
diff --git a/developers/apis/messenger.rst b/developers/apis/messenger.rst
@@ -89,6 +89,9 @@ Here is a little summary to the kinds of messages you can send manually:
.. _NAME_002dmessage:
+NAME-message
+^^^^^^^^^^^^
+
NAME-messages can be used to change the name (or nick) of your identity
inside a room. The selected name can differ from the identifier used to
select your private key for signing and decrypting messages.
@@ -133,6 +136,11 @@ combination.
DELETE-message
^^^^^^^^^^^^^^
+DELETE-messages can be send via the separate function
+``GNUNET_MESSENGER_delete_message`` which will handle linked deletions
+of messages automatically. Messages can be linked in cases the content
+of one message requires another message to co-exist.
+
DELETE-messages can be used to delete messages selected with its hash.
You can also select any custom delay relative to the time of sending the
DELETE-message. Deletion will only be processed on each peer in a room
@@ -143,6 +151,52 @@ chained hashes connecting the message graph for potential traversion.
For example the check for completion of a member session requires this
information.
+.. _TICKET_002dmessage:
+
+TICKET-message
+^^^^^^^^^^^^^^
+
+TICKET-messages can be send via the separate function
+``GNUNET_MESSENGER_send_ticket`` which will verify whether the selected
+private key of your identity matches the key used to issue the ticket.
+A ticket contained in such a TICKET-message will be sent privately to
+its regarding audience. That audience will be able to consume the
+received ticket via ``GNUNET_RECLAIM_ticket_consume`` to gain access to
+selected attributes and their stored values.
+
+TICKET-messages require the usage of the RECLAIM service of GNUnet to
+issue, revoke and consume tickets. Revoking tickets is independant of
+deletions inside the MESSENGER API.
+
+.. _TAG_002dmessage:
+
+TAG-message
+^^^^^^^^^^^
+
+TAG-messages can be used to tag or reject other messages in a
+communicative way. Depending on the level of publication the message
+fulfills different terms of functionality. For example if sent in a
+private way using your own public key as audience, it might be used to
+tag messages in a sharable way between different devices.
+
+Public tagging or private tagging shared with only one contact might
+reflect the communication of an own assignment or decision. For example
+it can be used to reject an invitation from another contact.
+
+Rejection can be expressed via a TAG-message that does not contain a
+tag or in other words the tag is an empty string. This is a special case
+for applications because it might translate into the rejection of
+contacts or blocking of them.
+
+Tagging or blocking of contacts depends on the message which is the
+target of a TAG-message. If the tagged message is the latest
+JOIN-message of another contact, the tag will be interpreted as tagging
+of the regarding contact. The same way a rejection of such a
+JOIN-message will be interpreted as block of the contact.
+
+Unblocking or untagging can be done via deletion of the selected
+TAG-message.
+
.. _Member-sessions:
Member sessions
