Q drops specifically state Q can not first verify/re-verify with TRIP, it's against the National Security Charter.

3619

Nov 21, 2019 10:18:33 PM EST

Q !!mG7VJxZNCI ID: 000000 No. 7359408

>>7359370

/pf/ was taken down [cleared of content] just prior to platform TERM [specific reason].

NAT SEC [charter] prevents use of 'keys' to establish IDEN via public utility/domain - non_reg.

Formation of 'clean' board possible to lock in trip(s) issues w/ safeguards.

Q

Q posted on /QR/ and got the 0 Delta, they then waited for anons, who used to watch all of PDJT's social media to catch it. They didn't, so Q nudged anons with WATCH POTUS. They still didn't, so Q directly pointed at the DROP that had the 0 delta. Once anons (Possibly Dan Scavino himself) pointed out the 0 delta and confirmed it, Q posted on /hivemind/ because /hivemind/ has TRIPCODES enabled, and /QR/ has tripcodes blocked. Q couldn't set a new TRIPCODE for initial verification, it is against NAT SEC charter. It says it in drop 3619, check for yourself

The clean board, /projectdcomms/, meant to use to establish a new trip is no longer in Q's control, as soon as Babyfist posted there it was no longer in Q's control. THAT WAS THE POINT OF THE BABYFIST DROP. THE MOMENT THAT HAPPENED, Q COULD NOT USE THAT BOARD FOR VERIFICATION BECAUSE A CIVILIAN HAD POSTED ON IT. AND IT IS THE REASON THAT BARON OF ARIZONA IS GOING AROUND SAYING HE IS THE NEW BOARD OWNER OF /DCOMMS/. AGAIN Q DROP 3619

Whitelists only allows you to post a "whitelisted" trip on said board. There is no such thing as "excluding/whitelisting" a trip from the SALT rotation. The fact Jim lied about this is the second biggest red flag next to the secret SALT rotation to begin with.