Anonymous ID: fd6c21 Aug. 3, 2019, 7:47 p.m. No.36284   ๐Ÿ—„๏ธ.is ๐Ÿ”—kun   >>6361 >>6364 >>6376 >>6669 >>6747 >>6830

Just gonna pickle off this liddle thought-bomb

 

Anons, great freakin' digging , as always. I been outa da loop for hours and I see you guys have already torn apart the El Paso event and are well on the way, collectively, to finding all the DS fuckery discrepancies.

 

<But what stinks about this is how shallow the whole event has been. Almost like summon wanted the best diggers on the planet distracted from something else.

 

>Query: is anyone watching the back door?

 

Something about this tells me it was diversionary. Aimed at us.

 

Not encouraging a cessation of digs...

 

Just saying check yer 6

Anonymous ID: fd6c21 Aug. 4, 2019, 9:28 a.m. No.36604   ๐Ÿ—„๏ธ.is ๐Ÿ”—kun   >>6635 >>6671 >>6748 >>6831

So, I went back and looked through Q's drops from Aug 1 through 15 2018. Here are some interesting things of note (drop#, date, item of interest summarized):

 

  • #1812, 8/3/18 reminds FBI of their official oath to the country, 1 yr delta to the El Paso FF attack.

 

  • #1817, 8/5/18 warning to Anons about 24-hour FF cycle, "be aware of your surroundings". If we're 2 days ahead in the plan, arguably that warning was 2 days ago. However, it's also possible this is a wave of FF flags with worse tomorrow and we really need to check 6 everywhere.

 

  • #'s 1819-20, 8/5/18 Q updated and confirmed his tripcode. Possibly a 1 yr delta signal related to Q's recent house cleaning on /pf/??? Pure spifball here, no instinct or logic - just something in the back of my head told me it might be worth the mention.

 

  • #1827, 8/9/18 This one's potentially YUGE!!! BIGLY!!!

"Comfy? Previews are over. Showtime!"

 

>Which is immediately followed by...

 

  • #1828, 8/9/19 Q names the conspirators in Spygate/Russia hoax. This one leads me to believe that, if #1827 comes out 8/9, it links EVERYONE listed in brackets. Which is A LOT.

 

There were a few more of interest, but I'll leave it to you frens to look/judge for yourselves.

 

<Trying to get ahead of the cycle. I'm so tired of the FF bullshit

Anonymous ID: fd6c21 Aug. 4, 2019, 11:06 a.m. No.36673   ๐Ÿ—„๏ธ.is ๐Ÿ”—kun   >>6675 >>6684 >>6688 >>6690 >>6748 >>6831

>>36598

 

Jus' checked https://twitter.com/EPPOLICE/status/1157698560126857217

 

Now it says 1:03pm. Cap related.

 

How stupid is that?

 

El Paso Anon around? Can you do a public records request from your 911 on when the shooting was first reported, as well as a request to the EPPD Public Information Office (D. Petry is listed as the head guy per the EPPD website's 2018 annual report) to get when THEY say that tweet was sent out?

 

b/c I'm pretty sure the good people of El Paso would be right pissed if the EPPD first twatted about an active shooter

 

3 hours after it started

 

>Betcha they won't live to cover up for @Jack and his minions at Twitter.

 

<I guarantee you

Anonymous ID: fd6c21 Aug. 4, 2019, 11:10 a.m. No.36675   ๐Ÿ—„๏ธ.is ๐Ÿ”—kun

>>36598

 

Lemme correct a mis-spelling in >>36673

 

>Betcha they (referring to the EPPD PIO) won't LIE to cover up for @Jack and his minions at Twitter.

 

Imagine the dilemma. They have no reason to say, "Yes, we twatted that 3 hours later than the reports." Jobs get lost over that crap.

Anonymous ID: fd6c21 Aug. 4, 2019, 1:30 p.m. No.36805   ๐Ÿ—„๏ธ.is ๐Ÿ”—kun

>>36684

>>36688

 

Guise, it would be nice to notify these orgs about the twitter timestamp monkey business and see what they have to say about them.

 

If they can't change when these reports were made (assuming they were made prior to the changed twitter timestamps)

 

<Then we can turn this around on @Jack