Did anyone around here look into the stuff "notQ" posted ?? … and what's with the "[1] OWL [1]" thing ? Is it always 17 minutes wide ??
Checked the signature, and the guy had his first appearance on /qr/ in bread 1107 (pic), then again in 1799 >>1434135
Mentioning it because I got curious: Didn't care much if legit ot not, but notQ wants to communicate something, and it's related to the Q-Clock, which is why I looked into it and put it here.
DEFCON == DEFine CONFirmation
goes along with some SECURE CONFirmation
DEFCON gives us the MarkerType (i.e. primary or secondary), and if that's so, then there can ever be only a DEFCON[1] or DEFCON[2].
Also, we get a SIG. SIGnal is either the minute mark # of some tweet/post, or the delta between two {PAST}.CONFirmed TWEETs
When we get a trip code & it's valid, then we get secure(d) drops (from Q, of course). Also, drops might only occur when it's secure to drop them. During times of ongoing operations, it may not be secure to drop anything ("BLACKOUT NECESSARY.") ....
notQ appears to use Moutain Time (if accidentally or intentionally) -- whatever Denver or Utah may mean to anyone of you ....
So if you ask me, this guy tries to teach us something, and it's unlikely I'm the only one under the Sun to see this. Did anyone look at his "Solver" image or try to decode that "_EX" (example/exercise) from recently (pic)?
>>1676034
Found an "owl" ... lol. Not seriously though, but when reproducing notQ's example with the 07:24 p.m. Goodwin tweet ("[15]"), which confirmed the [1] marker >>1676034, something distantly related to some "owl" emerged, when arranging all 24 letters of the greek alphabet around the clock in a regular manner. The mirrored markings are drawn as well.
However, should indeed >>1691775 apply (i.e. two mirroring operations with orth. symmetry axes), then that should be identical to a 180 deg rotation.