-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow file uploader to redact file from server #5025
Comments
so redacting a forwarded "copy" of the event might lead to the original being unintentionally deleted? (possibly if the original sender reposted using forward) |
I thought forwarded events were marked as being forwarded, but it looks like they aren't. I guess if you redact an event, it could prompt the user to ask whether the file should be deleted too, or if it should just redact the event. |
they are not, and yeah sure it should ask, but then it'll need to make clear that it'll delete forwards and potentially the original too |
A case to consider (which is common with moderation): Someone else redacting your message, across homeservers. You won't be able to tell the other server to delete the file. |
Closing in favour of single tracking issue: element-hq/element-meta#398 |
so that the file itself is removed, rather than just redacting the event pointing to the file. This would require:
To figure out:
Note that this may result in forwarded events pointing to no-longer-existing files.
(based on conversation starting from https://matrix.to/#/!DgvjtOljKujDBrxyHk:matrix.org/$15052324193420585vPeiO:matrix.org)
The text was updated successfully, but these errors were encountered: