|
|
|
|
|
by temp512345
1230 days ago
|
|
It is exactly remembering the pixels. Just not all of them and it obviously fills in gaps (more hair as mentioned in a another post). You can consider the way it stores those pixels as a lossy compression format. If I copy a music sample but I store a compressed version of it (mp3 for example) you will not find the original bits in my database at all. I am still violating copyright. |
|
To extend your musical analogy, it's remembering that many songs are in 4/4 time, and that major chords sound appealing.
Also, were you to compress anything, an mp3 or a picture, in a lossy fashion, to that degree of compression (~10^-5), you would no longer have anything resembling the original. The audio would be glitchy noise, and the image would be a scattering of apparently random pixels a few pixels wide.
Here's the thing - I empathize that this is disruptive in a very similar fashion to a tool that does store compressed copies of the work in question. It is capable of doing the same kind of damage. There's a conversation to be had there - but it's just not compression. That's not how the thing works.