Quote:
Originally Posted by cuzzyman927
I don't mean to keep beating this issue, but if the CRC-code is active as a countercheck, then why is the image still active and accessible at the other site from which one downloaded it, and it is only not until when attempting to upload it to a host (say to post at VEF) that one now finds and is notified that the image is banned? If the image is banned then it should not even be at the other site.  |
Images are almost always at imagehosts, not at forums. So, this would only be confusing if it is up on the same image host which declares it as banned.
However, there is an explanation even for this scenario: images get often re-uploaded. A standard strategy for an image host to deal with a takedown notice would be to (i) remove the image, and (ii) stop further uploads of an image with the same code. However, that does not include older uploads. For example, someone might have downloaded a picture and then re-uploaded it with the same host. If then one incarnation of the pic is taken down, another may well survive, because they are not looking for other pics that are already up that have the same code.
Would that be an easy thing to do? Depends. If the database stores these codes for all pics then it would be easy. If not, this would be a horrendously complex operation. It is also possible that they now record the code in the database, but they did not do that originally - in which case many older pics would have a NULL entry in that database as code; in other words, the pic has a code, but the database does not know it.
Of course, because the database stores the picture and the picture contains the code, the database somehow stores the code anyway - but not necessarily in an easily accessible form. To begin with, the images themselves sit on external memory, not the database itself - that alone slows things down by a factor of 500-1000 these days. In addition, there would be no hashtables to access this data quickly - you end up with a linear search on data that may be millions of gigabytes...