Anonymous ID: 2fbd5c Dec. 11, 2019, 9:11 p.m. No.7486681   🗄️.is 🔗kun   >>6715 >>6749

>>7486627 (lb)

They can not be originals, otherwise they would have checksum identical with the filename automatically given by 8chan (on the left hand side above the image).

Your Freedom.png has checksum

02869f5d774c84366f96f472b1a7ca378ea8b454ac60cc2beeb5c556a30f551d

You can check it yourself for example at: https://emn178.github.io/online-tools/sha256_checksum.html

Q's original had sha256 checksum

a7ffb193423f0a5573ceeefe7c2a7863d1fc6d1559e28d93af78f63e36cdceed

 

There have never been any collisions reported for sha256 hashes, i.e. no two different inputs give the same hash, and no two identical inputs can result in two different hashes.

Anonymous ID: 2fbd5c Dec. 11, 2019, 9:35 p.m. No.7486817   🗄️.is 🔗kun   >>6836

>>7486715

>leftmost link is always the auto-assigned filename

Yes exactly, and if you'd tried it you'd have seen that the auto-assigned filename is identical with the sha256 checksum (+the image extension, e.g. ".png")

This is the easiest way to make sure that it is the original, entirely unchanged image.

 

Here is another example:

Your "Santa-with-hammer-signed-by-QA.png" has sha256 checksum of

6a5741ec6e689a8f3f58c7479beff8c0fcff9bebed8e6b6b99d313eab3b07970

the original file from the anon quoted "Hammer_time.png" has checksum

15b3aa3ccad4b28b479401d3df2caf66858c4e1438611f059b6fafd17f78e78f

(Posting it to prove the point, see left auto-assigned filename of pic2)

 

There's many more examples of that in you gallery, just checked some.

Something in these images is different, that's why the differing checksums.

Again. easy to check it yourself for example at https://emn178.github.io/online-tools/sha256_checksum.html

Anonymous ID: 2fbd5c Dec. 11, 2019, 9:45 p.m. No.7486871   🗄️.is 🔗kun   >>6909

>>7486836

>How can they be different

I don't know how or in what particular details they differ, I'm just saying they are different, and the sha256 checksum is a unique, reliable indicator for that.

8chan/8kun doesn't just arbitrarily name images. It uses the sha256 checksum of the original file the user uploaded as demonstrated above.

Anonymous ID: 2fbd5c Dec. 11, 2019, 9:57 p.m. No.7486928   🗄️.is 🔗kun   >>6950 >>6973

>>7486909

>Yes it does, so does 4chan.

No. 8chan/8kun does NOT arbitrarily name images. Neither does 4chan.

8chan assign filenames by their sha256sum, 4chan by the unix-timestamp (i.e "unixmilliseconds" that means milliseconds since 1970-01-01)

But go right ahead, I'm tired of this. You seem to know so much and believe whatever you think you "know". Kek!

Anonymous ID: 2fbd5c Dec. 11, 2019, 10:15 p.m. No.7486979   🗄️.is 🔗kun   >>6996 >>7033

>>7486950

You know so much, I don't think there's a need for me to explain anything.

Here's another "arbitrary" 8kun filename just for you which I can predict easily:

49b9b5f485f8bfec3345a150ef3a09230a837420356c27b85162bdebff90f008.jpg

 

If accuracy is so very important to you, you'll be able to figure it out, one day, maybe ….