Most interesting, that board freeze yesterday – was about to post updated clocks & tweets when it happened. For as much as I could see, as of the time of writing this, it's still valid & up to date.
As I said, since anons appear to be using your spreadsheet I took some time to check (some of) it.
Checked the Q post timestamps only for now, made a pastebin with results that do not correspond to what I could find in the archives:
pastebin.com/2f5AJArW
Some explanations as to the procedure & observations:
You have the same number of posts as qanon.pub – so for the examples below, I used qanon.pub for cross-checking with the three timezone html & your results.
Please don't simply assume the remarks in the pastebin are true, and instead check if I have done the cross-checking correctly.
For most parts, we're assuming EST neglecting DST. Most of your timestamps do not ignore periods of DST (i.e. are in EDT).
This wouldn't matter for deltas much, if it'd be consistent (b/w tweets & Q posts).
However, during periods of no DST, most of your timestamps are still one hour off, which clearly is incorrect (timestampwise).
Example: [Line 446] stamp is: 12-23 13:13:38 – Q posted at: 12:13:38 (EST)
For the above reason, I subtracted one hour from all of your timestamps, and compared the results to what I find in the archives. The results in the pastebin are those that nonetheless I could not locate in the archive.
This means, that most of your entries during times of no DST still need correction (1hr), even if they're not explicitely mentioned in the pastebin.
There are a number of additional errors.
Examples:
[Line 2] stamp is: 18:15:28 – was actually posted 18:15:48 (EDT) or 17:15:48 (EST)
[Line 224] stamp: 11-23 00:12:46 – actual time of post: 11-23 23:12:46
(in above example not only the hour is off by one during non-DST, but also the date is wrong, when one would account for the 1 hr diff)
[Line 1291] stamp: 04-27 23:52:57 – actual stamp is: 22:57:57 (EST)
On a side-note, and so you know that I do not mean to belittle you in pointing out these discrepancies: My ego is only as big as what I know & can, and I have learned quickly that there's too much I do not know and can not do (masterfully). Not being a cock, as in male chicken – more like a well-meaning Lion actually. If you need more help in correcting your spreadsheet then let me know. For now, I won't put it in the resources section unless you manage to correct it before this bread is full. In case you're willing to correct your work, please let me know if you want me to check the realDonaldTrump tweets too.
In case you want to correct your work, please also consider importing from some text source as this would exclude human error & save time. It's not hard to learn and I (or other anons) can probably explain it to you.
I like it! Thanks. Even though I had to use the grammar book to look up present perfect, and if it also means that it continues in the present.
Another small, but interesting fact from the department of numberfagging:
From 10/05 until tomorrow, 07/29, it's 297 days. Not that it'd be of any further special interest though … ;)
Thanks again!
Posting both versions of the updated (blank) Q-Clocks & realDonaldTrump tweets.
Since we're through the clock 71.7% and the bread's going to be full soon, I also add an updated pic for the postMarkers, as first posted in the beginning of this 2nd clockThread.
… which after 10secs got outdated … lol.
POTUS is up early on this beautiful day! Good Morning to everyone!
If needed (more than trying to understand what the clock is all about), then I could start working on a piece of software, that does (some of) that.
Not sure about the online access to qanon.pub – I'll certainly start with an offline archive off posts, but it'd be based on Qt, which would make it compilable for all platforms, incl. mobile devices.
It won't be done fast (like in a day), however – might take a week or so ….
Don't be hasty, friend. Even though it will surely be useful to have someone look over it once it is running (in some way).
Usually I work as a single-developer, and don't publish code untested (i.e. undebugged). However, since this is an open-source project (and malware exists and bad people too) I will surely make the sources available, once I'm ready to publish – possibly on a platform like github or such.
Here's a snapshot of the most general layout of the GUI as it could be useful & simple (w/o colors & likely subject to change while I work on it).
While I intend to build in functionality for online fetching of posts (primarily 8chan), I might have to re-consider which from sources.
Maybe other experienced clockfags want/can also chime in with suggestions or ideas of things that may be useful to add.
Agreed. Useful for normies & new clockfags. But, like it's been said, only the most basic of the beginning – not a proof of ( the ) concept.
04/19 ("13min mark") may also have to be added.
Apart from that, I don't quite buy into the last one (as adding up numbers is somewhat arbitrary – e.g. why not use their digit sum & end up at [:13] or [:04] ?) Also, why did Q add the "[0]" in unmistakably clear marker notation?
What the anon >>2352621 shows are actually two concepts:
(1) One saying that we have a continuously running clock with each passing day corresponding to a minute (and thus 06/03 is 14:58 when 12:00 is at [:00] marker on 12/07.
(2) The other (related, but more generalized) concept is simply that days correspond to markers irrespective of the hour as pictured in the Q-Clock (i.e. 04/07 is at marker [:01])
So, yes, according to (1) today would be 03:55/15:55, BUT:
Out of the ~1800 Q Posts, there are only four occurrences that we've got a Q Post at the time that the clock (HH:MM) would have shown. Those are:
→ 19-Dec-2017 00:12:02 (EST)
→ 06-Mar-2018 01:29:38 (EST)
→ 21-Apr-2018 14:15:51 (EST)
→ 03-Jun-2018 14:58:29 (EST)
These dates are 77, 46 & 43 days apart, respectively. Today we're 57 days after the last of these dates.
Not saying that (1) isn't true (the observations exist), just saying they are rare – and we haven't figured out the logics behind their occurrences yet (if any).
Hope so too! Thanks!
Will try and split my time in order to spend more on understanding the clock, than developing a software (when Q Post sources are a dime a dozen).
Re funny webpage: It had been changed …. only checked today, last time probably a couple of days ago – so I wouldn't know when the change occurred.
It's the Questions that drive us …. ;)
Ok then, thank you. I take it 03:55/15:55 are (for most parts) irrelevant then.
Listen guy, only once I'll say this: For me you're nothing but trying to keep us busy, and it would have almost worked, as it would have taken us a lot of time figuring out/realizing your "cracking" of the hexadecimal code "secrets". >>2191326
In >>2356708 you come with your "Q talk" about things that are irrelevant – read >>2356274 carefully again, in case you do not understand.
Nobody was talking about minute markers being irrelevant, as these – trivially – correspond to the minute markers (i.e. days) on the Q-Clock. So long, buddy – until I recognize you again in the next bread … ;)
Here are the Notables collected so far from this bread.
Tried my best not to miss anything – but probably I did. There's still room left in this bread for suggesting more, removing some or making changes.
I intend to leave the header in the dough as it as (unless someone objects), and also add a small section of useful resources (which is also posted below).
Notables from last Bread
>>2021755 — Quadruples of shared markers (visually)
>>2031990 — Shared markers (colorized) with number of matching Q posts
>>2033357 — Is there a word code hidden in the Q Posts? (last words)
>>2038757 — Old Tweets Matter (also >>2044788 )
>>2039498 — The "Last Word" Challenge is on, also >>2036407
>>2040071 — Q-Graphic for 15mins Deltas (markers [00],[15],[30] & [45])
>>2040224 — Towards solving the "Last Word" Quiz? (shared markers [01][59][29][31])
>>2050323 — The "Last Word" Quiz gets automated & tabulated (avoiding human error)
>>2052761 — "Ordering is critical." – The Order of Minutes & Seconds
>>2083612 — Concerned the Q-Clock is a "giant" slide? Read >>2084486
>>2087420 — Extending the "Time Travel Guide": [2] Q Chapters & the Q-Clock calendar (also >>2097059 & >>2104047 )
>>2102778 — "News unlocks the map." – more examples
>>2140561 — Trying out "+1 +5" – does it work with shared timestamps?
>>2156265 — July, 14th: "Data mine NP +1 +5" decoded & confirmed previously? (see >>2104150 & >>2134025 )
>>2161883 — Q-Graphic for shared markers [50][10][40][20]: Advanced Faggotry
>>2173020 — A 40 seconds Q Graphics & clock: There should be no F A T in FANTA (Facebook/MZ, Alphabet/ES, Twitter/JD)
>>2185347 — "Look there, or [here], or there, truth is behind you." (also >>2186516 )
>>2193853 — "Dark to LIGHT." or Lights out in the WH: the :07 Delta
>>2206865 — POTUS has the power to "unlock": Time Travel Guide to understanding present, past & future (also >>2208306 & >>2209516 )
>>2209549 — A "two post curio" & another approach to the Map: The Vatican (also >>2212819 )
>>2221272 — Towards a Q-Clock 101
>>2221677 — POTUS is talking to US!
>>2225799 — Visualizing the three (or two) mirror theories
>>2232057 — "Follow the pen." – Re-post of the "StarWalker Extreme" fountain pen
>>2236853 — The "unlocking" power of POTUS (cont'd)
>>2265457 — POTUS at VFW: "God Bless the USA" – From Sea to Shining Sea approx. 01 hr 07 mins after Q (also >>2268112 , >>2269306 )
>>2277240 — Trump adresses Rouhani in All-Caps: Q-Clock Graphic
>>2314624 — 8 instead of 4 shared markers for an accelerated timeline? (also >>2315963 & >>
>>2352446 — The clock is NOT for making predictions! & There's a reason it hasn't been confirmed directly.
-→ A lot of work done related to the possibility of a "word code" in Q Posts – refer to archived bread for more
-→ A large number of images not mentioned which are helpful for understanding the "Time Travel Guide" – refer to ID ad10dd
############# Break ###############################
Some Useful Resources
→ Convert timezones depending on date — www.timeanddate.com/worldclock/converter.html
→ Compute number of days (+ other units) b/w two dates — www.timeanddate.com/date/duration.html
→ '''Online Cipher Tools for various ciphers — rumkin.com/tools/cipher
→ HTML of all Q Posts for offline use (incl. headerLines in three timezones) — mega.nz/#F!iLwgXKRb!XvA-cUt5-8XyRPlgoVH-FQ
→ Archive (copies of 8chan HTML, incl. images) of previous clockBreads — mega.nz/#F!uaoQEKDD!bzufzJagvg7_nHz6Oyftng
Same here – calling it a day. Posting updated blank clocks & realDonaldTrump tweets.
As for the Notables: Corrected "Trump addresses" & added the correct reference for the "accelerated timeline", which was meant to be >>2327402
With about 30 posts today, I'll leave the dough to rise overnight, before re-checking new posts, comments/additions, and baking the new bread tomorrow.
Thanks for the comment! Made me chuckle quite a bit and almost spill the covfefe. lol.
Gave the laptop a hug too, hoping it won't let me down for the rest of the ride.
A peaceful Good Night to you.
Godspeed.
Thank you. Even though it goes w/o saying: It did catch on – at least with me it does.
Still haven't given up on putting it all together (in a consistent & concise manner), like I began to do above (in "so much text"). Was just dumb enough to follow some ideas that were nothing but a distraction, most likely …
For context & to make sure numbers are correct (always verify!), here some historical dates & markers:
04-Jul-1776 – 88,179 days back from 2017-12-07 → [:21] on the clock
26-Dec-1776 – 88,004 days back from 2017-12-07 → [:16] on the clock
07-Dec-1941 – 27,759 days back → [:21]
22-Nov-1963 – 19,739 days back → [:01]
(via: www.timeanddate.com/date/duration.html)