[–] [deleted] 0 points 0 points (+0|-0) ago 

[Deleted]

0
0

[–] RevanProdigalKnight 0 points 0 points (+0|-0) ago 

Did you consider taking MD5 hash sums of the images that are uploaded and then, when there's a hash sum collision within a period of time (say X hours/days of the original upload), prompting the user about whether or not they still want to upload it?

Another nice thing about running an MD5 hash sum check is that if there is a collision when the user says yes to storing the image on your servers, you can run a file comparison then to see if the images are actually identical, and if they are, just linking to the original to save disk space. You can even have the client browser be the machine running the hash generation to save on server use, just have it POSTed over with the image, or send it over before even confirming the upload.

0
0

[–] Stavon 0 points 0 points (+0|-0) ago 

I'd use the sha1sum as filename and create symlinks or database references to it. But of course with such a filename you can also block reupoloads.