You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We implemented the Voice Broadcast feature by following the current spec.
This spec describes an intermediate solution to implement voice broadcasts based on a chunk of voice messages.
We are supposed (client side) to be able to delete an existing broadcast. The user will see a unique tile in the room timeline whereas several events are concerned. We may trigger a m.redaction event for each event in case of deletion, but this seems irrelevant. It would be more efficient to trigger a unique event to delete server side the whole broadcast.
It would be great ta add a flag in m.redaction event to be able to delete all related events to the targeted event.
This was the reason of the MSC3912 creation, that we should implement now
Have you considered any alternatives?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Your use case
What would you like to do?
Use MSC3912 (details) to delete server side all the data of the deleted voice broadcast
The server capability are retrieved: https://matrix.org/_matrix/client/versions
Why would you like to do it?
We implemented the Voice Broadcast feature by following the current spec.
This spec describes an intermediate solution to implement voice broadcasts based on a chunk of voice messages.
We are supposed (client side) to be able to delete an existing broadcast. The user will see a unique tile in the room timeline whereas several events are concerned. We may trigger a m.redaction event for each event in case of deletion, but this seems irrelevant. It would be more efficient to trigger a unique event to delete server side the whole broadcast.
It would be great ta add a flag in m.redaction event to be able to delete all related events to the targeted event.
This was the reason of the MSC3912 creation, that we should implement now
Have you considered any alternatives?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: