So what fucking hash do archives use to find the same images?

>>55885853
It is MD5.

>>55885867
The MD5 for my picture in OP is 275c81beb3af06153c8680bf682854e4

https://archive.rebeccablacktech.com/g/image/J1yBvrOvBhU8hoC_aChU5A

Hash: J1yBvrOvBhU8hoC_aChU5A

its not the same

CRC32?

>>55885986
nope, it's "bedd13bf".

this is so fucking weird

does no one know

http://www.commandlinefu.com/commands/view/3555/find-duplicate-files-based-on-size-first-then-md5-hash

>>55885918
it's J1yBvrOvBhU8hoC/aChU5A== you fucking retard what do you think bin2hex(base64decode(md5)) would look like

>>55886718
"MD5 HASH" J1yBvrOvBhU8hoC_aChU5A
Actual MD5 HASH 275c81beb3af06153c8680bf682854e4

you are the one who is retarded here kiddo

File: Qm9YMdO[1].png (16KB, 879x49px) Image search: [Google]

16KB, 879x49px

>>55886768
https://ideone.com/cN67V4

fuck off arse

File: 1465836071442.png (22KB, 723x576px) Image search: [Google]

22KB, 723x576px

>>55886804
https://emn178.github.io/online-tools/md5_checksum.html

see fo yourself

>>55886825
it's correct checksum, what the fuck are you trying to say? that you can't parse base64'd md5 from json propertly?

>>55886861
no it's not

>>55887026
then what is?

>>55887062
some fucking bullshit that's not MD5

>>55887095
do you even know what md5 is?

>>55887120
yes, checksum

>>55887265
do you know what output it produces?

>>55887275
md5

File: table flip.jpg (71KB, 500x262px) Image search: [Google]

71KB, 500x262px

>>55887479