Pete/Pcb21 wrote:
Allan's solution - disallow overwriting of images - would solve the problem completely, be trivial to implement (we already check for pre-existing pictures of the same filename), and has only the minor drawback of perhaps using a bit of extra disc space now and then.
I don't like this solution at all---overwriting images is frequently used to upload revisions of images while leaving a revision history. For example, maps may be edited, darkened/lightened, or otherwise tweaked, and it's useful to have the revision history available, or to be able to roll back to a previous revision.
If there's a problem with a particular image, we could instead use protection of images analogous to the protection on pages, rather than throwing the whole revision system out.
-Mark