It is impossible to upload two files if both have the first 50 chars and the suffix equal.

If you upload two files with names like these:
looooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong-1.jpg
looooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong-2.jpg
Only one file would be uploaded, because the normalizer would create the same name for both of them, and both files are uploaded requests so there is no straightforward way to differentiate between a two file upload and an overwrite.
One could store the original long name in an annotation. But this could mean that people get confused why a fileupload sometimes generates a new file and sometimes not, because the information of the original long file name is lost.
maybe uploading images should not get trunctated at all when using collective.quickupload.
There is a mailing list discussion to this topic: http://sourceforge.net/mailarchive/forum.php?thread_name=CAFefbnHdyfbD%2B7xs69JUxkgMLr3gf1mNOUGYnB5Sudb-8NXYgg%40mail.gmail.com&forum_name=plone-users

Start by tracing the filename normalizer and the uploaded-request handling described in the issue, then read the linked mailing-list discussion for the unresolved design context. Done should distinguish uploads whose long names share the same prefix and suffix without silently treating one as an overwrite; the issue does not name a file or test to run.

Written by the indexing model from the issue text.