DJT rally "mistake" decode…[B]en for [m]en
Given the disputes about whether DJT has confirmed the recent Q posts, I went back to carefully rewatch the Mendon rally:
https://rumble.com/v19xka7-president-trumps-full-speech-at-the-save-america-rally-in-mendon-il-62522.html
At 8:40 PM, where he is supposed to say "men", he actually says "Ben".
The posted video snippet is from RSBN, and you can listen for youself.
To get that clip, I checked my Network tab in the developer tools to find the right mp4 link and saved the whole video using youtube-dl (as it couldn't decode the original link).
Then I cut the snippet with Avidemux, and saved the audio track.
To get the waveforms shown in the graphic, I put that audio into Audacity and took a screencap.
It is hard to "hear" this sort of "error" unless you are directly listening for it, but DJT has done this sort of thing before.
(I think he overtly said something about Q at a rally in West Virginia once, but it was "hidden" by the "intended" meaning.)
In this case, the comm is hidden in a "red meat" line, so most anons were focused intently on the content, not the sound.
The upshot is that DJT says "Ben" and not "men".
Then the issue is how to decode that, and I offer two decodes, and they both work.
One points to a Ben Garrison Q post, and the other gets going with Ben Franklin.
The 8kun javascript part of the decode might seem to come out of nowhere, but I knew about the timestamp there from earlier looking into what was going on with the ID numbers on Q's posts.
There was a question about why the TOR posts would show a normal ID on mouseover, and part of the answer is that the mouseover event is calling a function in main.js.
See: 8kun.top/main.js
But there may be further things to discover there.
There do seem to be oddities in the comments at the top, but I did not want to go too far astray (and plus I am not an expert on this).
There seem to be extraneous comments (this slows things down) and the seeming juxtaposition of "polish notation" (operators in front) and Polish language may just be "geek humor" or it may be a subtle pointer to Q26.
The Baylor Lady Bears tweet also did not come out of nowhere.
I think it is in one of the clockfag graphics that gets posted every so often.
I am not a clockfag but I do take a look at the graphics from time to time.
At the very bottom, I use the infamous "B" post in the decode because it works.
It works whether it was posted by a black hat or a white hat.
It was apparently deleted by Q at the request of an anon on the night that Q returned.
Jim Watkins subsequently made some comments on this, and it is from his post that I got the partial board log screencap: >>16581551 (pb)
(The projectdcomms board log is not publicly accessible.)
I do not have any idea what #112 was (if it ever existed) and I do not believe it was there earlier than a few weeks ago, if that.
It has occurred to me that some (or all) of the "board drama" may be a ruse.
There are some seemingly well-intentioned anons advising others against complex decodes.
But there is nothing wrong with complex decodes if they are accurate.
Q team drops the comms, and anons do the decodes, and if they turn out to be complex, maybe that is because Q team dropped complex comms.