Anonymous ID: e064a2 July 29, 2018, 10:04 p.m. No.2350001   🗄️.is 🔗kun   >>0149 >>0468 >>0636

ArchiveAnons and ImageDigAnons: Make sure you're getting the REAL original image!

 

Every file uploaded to a post has an MD5 checksum calculation for the real deal (JSON feeds have them hiding inside). Only the 2 circled links in the example attached will give you the ORIGINAL image that can be verified by MD5 to match. The other link (or a Right click -Save as) will give you a thumbnail.

 

Also, cloudflare caching does some "optimization" fuckery: They'll alter the file downloaded (even with the 2 "safe" links) to optimize for a smaller downloaded file. This will invalidate the MD5 check to the original uploaded file. Bust that caching crap by adding "?random1234crap" or something to the end of the image links in your archive tools.

 

I've checked a handful of the "full size original photo" stashes for both Q posts and ones digging for other stego clues. They're NOT the originals in most cases. I'm personally missing a handful for Q images, but slowly finding them. The nice part is if an original that was deleted get's re-uploaded to a post, the old 404'd links are supposed to come back to life.

 

Will provide clearer examples later this evening with Q posts - running some maintenance on my archive DB so can't get to anything for a bit…

Anonymous ID: e064a2 July 29, 2018, 10:14 p.m. No.2350149   🗄️.is 🔗kun

>>2350001

…also for note (I'm behind on the deleted drama, but guessing we have a censor happy BV…):

 

My archive critter is snagging stuff in real time-ish. Management would have to delete faster to beat it. If something turns up dig worthy in attached files, but it went poof odds are good I can cough it up. From about 7/15 onward…

 

TBH, I haven't even looked at what it's scraped in any detail yet, but I know it's up to 73GB of posts (2M+) and stashed original images (300K+).

 

Q did say archive offline, right? Kek!