[Feature] API to blacklist a hash or attach multiple hashes to an asset

[affectful]

I have searched the existing feature requests, both open and closed, to make sure this is not a duplicate request.

• Yes

The feature

In previous discussions it was declared that immich would not modify any original images thus changing the hash and it would be left up to plugin authors. However the API is not versatile enough to prevent modified (edited or recompressed assets) from being reuploaded. The author of immich-upload-optimizer made a new project to sidestep this limitation by making the user use some other form of backup to the proxy. This is not in line with the promise of having a plugin that could handle this feature.

I wonder if it would be reasonable to therefore add some type of way to prevent the original hash from being reuploaded when the server's asset was replaced with a new file and hash. The way I think that can happen if the server API exposes a blacklist of hashes to check against or if multiple hashes can be attached to an asset thus preventing reupload.

To re-iterate why this feature is useful, the videos uploaded from phones can have an unbounded bitrate quickly filling up user's online storage faster than storage costs can come down (recently storage costs have only risen).

Platform

• Server
• Web
• Mobile