Question: a "delete media" option e.g. for clean-up purposes

[8go]

• after downloading media to local disk, maybe a "delete" option would be helpful to "clean up" on the server side
• would be useful for archiving and reducing matrix server db size

[8go]

Anyone wanting to contribute? Anyone willing to provide a PR? Any contributions are ❤️ appreciated!

[8go]

Which matrix-nio AsyncClient API calls or logic would do such a media delete?

[8go]

See also:

• Need to be able to safely cleanup local content matrix-org/synapse#3479 --> using DB SQL scripts to do cleanup
• Delete old messages? matrix-nio/matrix-nio#308
• https://git.wehack.space/matrix-synapse-scripts/tree/mxclean
• https://github.com/mserajnik/synapse-purge --> https://sr.ht/~mser/synupkeep/
• https://github.com/matrix-org/synapse/blob/develop/docs/admin_api/media_admin_api.md#delete-local-media
• https://github.com/matrix-org/synapse/blob/develop/docs/admin_api/user_admin_api.md#delete-media-uploaded-by-a-user

HTTP API:

• curl -XPOST -d '{"msgtype":"m.text", "body":"hello"}' "https://localhost:8448/_matrix/client/r0/rooms/%21asfLdzLnOdGRkdPZWu:localhost/send/m.room.message?access_token=YOUR_ACCESS_TOKEN"

or

curl -XDELETE "https://SERVER_HERE/_synapse/admin/v1/media/SERVER_HERE/XMC_ID_HERE?access_token=ACCESS_TOKEN_HERE"
SERVER_HERE something like matrix.org
This curl requires ACCESS_TOKEN to have server admin rights (not room admin rights). Otherwise it returns:
curl -XDELETE "https://matrix.com/_synapse/admin/v1/media/matrix.com/XMCIDHERE?access_token=ACCESS_TOKEN_HERE"
{"errcode":"M_FORBIDDEN","error":"You are not a server admin"}

Building something around this REST API? But obly useable by server admins!

[8go]

--delete-mxc was implemented in commit 583a2bd

But as required by the Matrix API it requires user to have server admin permissions. See documentation.

Closing issue.

[8go]

Just wanted to add that I looked at the Client API (not the Admin API) and confirm that there is no "delete" operation for the content repository. So, I think what was implemented was the only available option.

See: Matrix Client API documentation: https://spec.matrix.org/latest/client-server-api