As in all the centralized messaging applications, the ability to delete or edit already published messages is desirable.
However, Waku2 does not have any support for this feature.
Solution ideas
One potential solution is to include an extra field in a waku message as a pointer to a previously published message. As such the new message will replace the message pointed by that pointer. in terms of store protocol, this means all the store nodes will replace the old message with the new one.
In waku2, for the sake of anonymity, we do not include nodes public keys (or any other identifying info) in waku messages (not even in the relay messages). This causes some issues related to access control while handling edit requests from users that are not authorized to edit a message (as they are not the author).
Problem Definition
As in all the centralized messaging applications, the ability to delete or edit already published messages is desirable. However, Waku2 does not have any support for this feature.
Solution ideas
EditMessagesimilar to what the Status app does. https://github.com/status-im/status-go/blob/f8c1422b374a145fa68a202cb85a61b36eee4c23/protocol/edit_message.go#L11-L27 The message incorporates the ID of the old message and this way the new content replaces the old one. The message-id calculation is based on the message and the author's public key https://github.com/status-im/status-go/blob/7343b1b50ceb77d14695d310ec9511f92b33cac3/protocol/v1/message.go#L26-L31Potenital issues
In waku2, for the sake of anonymity, we do not include nodes public keys (or any other identifying info) in waku messages (not even in the relay messages). This causes some issues related to access control while handling edit requests from users that are not authorized to edit a message (as they are not the author).