Can't "see" columns of numbers, and have little idea what your abbreviations are (and the numbers). Since you mention frequencies, and these are looked at in cryptography, I'm assuming it's some kind of a histogram.
Done this in EST for both, minutes [:MM] and [HH:MM] – still ignoring seconds ….
12:09 (a.m. & p.m.) stands out, with some others.
and [:59], right next to it (both 13)…
What's also interesting, on a 12 hr clock, there have been 107 (!) "HH:MM", with no post at all.
Don't like filling the bread with numbers, but for those curious there's a pastebin at: pastebin.com/SkY2LTe0
Not quite there yet, to exclude anything, which is why I made this pic – so anyone can have a look.
Have not thought much about it yet, but it looks somewhat autistic …. For a short explanation:
x-axis minutes [:MM] (60 of them)
y-axis hours [HH:] (12 of them a.m./p.m.)
black is combinations of [HH:] & [:MM] with no posts at all
blue is combinations of [HH:] & [:MM] with posts in both, a.m. & p.m
yellowish post only in the a.m. only
brownish post in the p.m. only
As for 107, not sure – just mentioned it 'cause it's an interesting number, and close to 108 as well.
Mixed up colors for p.m. & a.m. in above pic, so here's one with numbers to make it clearer.
Sums (a.m. | p.m.) drawn for minutes & hours on top/right. Sums reproduce the histograms in >1751959
Except hours 12/0 & 1/13 all appears skewed towards the p.m. Hours [04:] – [09:] significantly less a.m. than p.m…. A man's gotta sleep. lol.
Minutes [:11], [:17], [:23] & [:28] appear quite balanced in a.m. vs. p.m. But I'm not sure if it's helpful like that ….
Found 107 interesting because it's prime (28th), "combines" 17 & 10, and is close to 108.
For what it's worth, and since "playing-dumb anon" ( >>1735897 ) has demonstrated it before: Here's the sequence of [:MM] markers around the Q-Clock, when doing: for i=[0,59]; [:MM]=(i*107) mod 60
Posting it because all clock markers [1,2,3 … 12] are where they should be, except anti-clockwise.
No, no .. nothing to read. Simply a test of how the sequence of N_i=i*107 mod 60 would arrange around the clock. Should have drawn the clock anti-clockwise direction, because [:05] is at "11" o'clock position, [:10] at "10", [:15] at "9" o'clock etc …
Thus, mapping the minutes markers [MM] (not by a series of multiples of 17, but multiples of 107) interestingly reverses direction for these "primary" markers on a clock, which is a nice "coincidence", I figured.
>what do you mean by reverse?
simply the reversal of the 1,2,…12 clock markers, which coincincide with [:05], [:10], [:15], etc (pic) … unfortunately all the other minute markers appear "scrambled up" (pic)
Not ignoring the 107 … seems like a good number with its close resemblance to 17. Just running around and also doing other stuff.
Darn. Where's the owl … lol … Just wanted to point out that 2 changes pos w/ 10 & 9 w/ 3. Did I draw an owl?
Wouldn't know about "rules", probably not. But the thing with putting the minute hand where the day is, appears to work out.
There's the "13min mark" that goes well w/ that, the posting at 14:58 on 06/03, the pens, and many of the "daily clocks" posted in the general.
What I am missing, still, is some mechanism of selecting, excluding or ordering Q posts by way of some system that actually involves the timestamps.
While fine for "day-to-day happenings" apparently, above method of putting the minute hand on the calendar day doesn't make use of the actual "HH:MM" timestamps we have in the posts …..
With a good dataset & good tools it's really not much work. Chips are the slaves, so no problem. ;)
Wondered if "scrambling up" the minutes and/or hours through some mod 60 operation qould be useful, so that a more regular pattern would emerge ….
Also, checking the sequence (in time), how the initially all black grid got all the blue & yellowish squares may be instructive.
(also >>1763186 )
Q (as Anonymous, if that counts …) just filled one previously black square at 05:19.
thanks, still not there – have a back-log of bread. lol. Updating data & pics while reading bread …
Check for example >>1597885
Anon >>1563625 was persistent. Don't know if the idea had been floated before.
Would have to re-check when exactly the 111 days idea emerged, but was most convincingly indicated by POTUS' water-move at the FEMA meeting recently: 111 days b/w Q post ("Watch the water.") and date of FEMA meeting.
That thing with the two tweets, reminded me of the "Good[win]"-exercise a bit yesterday, when we got the "1" marker confirmed.
Yesterday's two times in a clock would look like this … the concept makes me think of a "curved mirror", with the center of the clock being the "focal point".
There's an updated template of the Q-Clock with recent posts marked in the calendar.
In case someone is curious about patterns and the number of Q posts in each of the minutes [:MM] & hours [HH:], there's also an update of that beautyfully useless pic in >>1760417
… and speaking about patterns, for the barcode fags there's an updated timeline of Q posts.