>>9041137

"luke lurks" too. ;)

There are a few images that have "non-displayable characters" in them.

Pull the keyword field from the metadata & see what it's encoding is??

You know I'm all about "it's in little pieceslike a puzzlethat we have to reassemble" (combine all the little "crumbs" of data into 1 file and that'll give us XYZ proof)

MANY Q pics (PNGs) will reveal a similar NDC string with stegano-red.

zsteg has spit out some interesting stuff, but I'm wearing of short string false positives like we talked about.

We've talked about IMAGE NAMES being important because Q (or the poster) can CHOOSE what they name the image before they upload it. This and the TIMESTAMP (to me) are the most important pieces of the posts (that don't have to do with the content of them–which truly could even just be "cover text" to conceal 'steganographic messages' utilizing timestamps and/or image names).

more to come!

>>9094189

This may be why "even if you DELETE Facebook, it STILL tracks you!!"

(because you still have things on your phoneespecially if it's Androidthat utilize that Google libs)

>>9085813

yes @ flags w/ diff names & sizes!

some are ~23 kb lol

Some are PNG, some are JPG.

I remember someone even mentioning that one of the flags had the WRONG number of STARS? (don't recall which or if this was verified though)

Another little "coincidence" is that the PAIN/Punisher pics always seem to come FIRST, and then shortly after, there'll be a FLAG pic.

PAIN = Operation?

FLAG = SUCCESS?

>>9085813

f768deaef22da979abcfb73c9175b54d71fcf891666c5449c1969c07c3cc8920.png

This is the SHA256 of the PNG above.

274534d7d1780203956040e16a2fd8712e21596c92d7ac2ecd959d0166f8a501.png

Grab all the flags, check MD5, SHA256, etc. and you can see what IS and IS NOT actually the same files.