(Posting early for maximum exposure - 177 will be filled in a minute).

This is mostly for future reference for other anons. In case you find the same thing happening to you, or something similar.

I'm about to decompress and analyze the second data block of the PNG file that Q posted. I got called away to give my roommate a ride to work. Got home, and an email came in almost immediately. It was from a very unstable, certifiable relative declaring that probably $10k worth of my stuff that's stored there (out of state) will be sold off, destroyed, or whatever happens to it. Two of the items are a Marshall amp and a vintage Stratocaster which I've had since 1980. The reason? I like Trump too much. This person has (thankfully) been extremely quiet for many months, and suddenly surfaced exactly now.

The email was from an absolute lunatic. Maybe on meth, I don't know. This is one of those people who is so driven by hate, and so pumped full of adrenaline that just seeing a photo of the person will make your skin crawl. Intensity like you've never seen, and all of it very dark.

The point is the timing. Just as I sat down to begin work on the decompression, this happens. I have no way of verifying the email was actually from the person claiming to have sent it. It probably was, but I can't verify. The timing of this is just not believable. Too perfect. Q always says there are no coincidences.

I don't claim to have any clue what's going on and it would probably do more harm than good to piss away valuable time trying to figure it out. Just be aware that this was no small attack (even if it wasn't physical, the fear of it becoming that way looms quite large), and it struck (not Strzok) at the exact moment I was about to start decompression of the second data block in the PNG file.

If you're ever about to do something that could be very important to our task at hand, keep in mind this kind of thing can and did happen. There is always the possibility that it's not related, but given the timing, that possibility is very, very small.

>>147007

Anybody coming in here and posting "I don't know if we can win" is immediately flagged as Black Hat, as far as I'm concerned.

The old tactics just don't work anymore. It's a new age.

>>147043

I already posted that you can remove the second data chunk entirely and the image displays exactly the same as what we see.

>>147055

I'm working on decompression now. If I survive the process.

>>147079

The bottom line is that Q is still posting for us. If we were any kind of major letdown he / they would not be.

As for a bunch of micro-managing female supervisors … I've been there, more times than I care to mention. It wasn't pretty.

>>147116

Oh well. Free speech and all. For now I'm concerned with what I'm doing.

>>147218

Many thanks. Keeping the "key post" but all that really is, is the name of the file as it was uploaded. 8ch renames it internally; the second name is the name the user had assigned when it was uploaded. But that could very well be the key, depending on what the contents of the second data block actually are.

I have the file loaded into my app, and I've skipped over chunks to the pair of IDAT chunks that hold the data. So the input, output, and memory requirements are all handled. Now it's just actual decompression.