MSC4113: Image hashes in Policy Lists

[MTRNord]

Rendered

Potential COIs:

• I do volunteer work for Draupnir
• I volunteer at the Matrix foundation for the website
• I do work for Nordeck

Signed-off-by: Marcel Radzio [email protected]

[MTRNord]

As mentioned in the MSC I am not sure how to best define actions in the MSC. Suggestions are welcome

[TheArcaneBrony]

Personal observations and opinions (based on original version):

1. use a dictionary format for types, so multiple can be specified in a single event (eg. i want to support md4, md5, sha128, sha256, sha384, sha1, sha3, ... file hashes)

• this also allows you to implement newer formats while keeping backwards compatibility, without having to send 2 million events per policy (/h)

2. the proposed format only works for images, so calling it "media" is misleading (is an audio file not media? how about a word document or a zip file?)
3. Perhaps a policy tags list may be useful? This would allow bots to decide an action based on that, eg. csam would be a ban but lewd imagery may not be, depending on the room it's posted in

[turt2live]

This also, unfortunately, creates a list of media that those bad actors will want on their servers. This is what makes this sort of feature difficult, and illegal in many jurisdictions: listing media which may contain CSAM, terrorism, etc is often as illegal as distributing the content itself.