>>2173888

There is the three-timezone single-file html for offline use, which is searchable in the browser (or command line, if you do that).

It is a machine-copy (i.e. from the sources as they were by an algorithm) and thus should contain little to no errors.

It's a zip file named "extractQ.zip" to be found in:

mega.nz/#F!iLwgXKRb!XvA-cUt5-8XyRPlgoVH-FQ

and contains all large version images and is linked correctly too (i.e. fully offline for all messages contained therein)

It also contains deleted messages (just as qanon.pub contains some of them)

Differences in nr of messages b/w this archive and the qanon.pub "standard" were listed in the last bread: >>2012483

>>2177072

Checked. And not understanding the many colorful lines, but surely got the message, and am enjoying the show doubly-good (++). Thanks.

>>2177438

>>2178150

It's less about the lines & colors, but more about posting this w/o explaining what it should be and how, for example, to select which markers to use when.

1, 5, 10 & 15 are quite well known (to us clockfags at least), and still I do not believe they have to be looked at all at the same time (or in the same clock).

With each marker, on avg, covering three days, you'd end up with a pretty large number of Q posts to search through, if you take minutes, day markers (and maybe also seconds) into account.

>>2178331

Sure, but why? Any indications?

We've found plenty of indications with the clock repeating the cycle after 60 mins/days.

>>2178487

Spend sooo many nights on the clock and days … just to see that, again, in the last night I didn't solve it, and to then, in the next day, chase the next idea by someone (which might have well been intentional disinfo solely to keep us busy) ….

Slowly coming to think that if we're supposed to solve it, then they will tell us.

Thinking about it – and seeing the anons having fun in the general, when I was trying to "solve" it – I was wondering how Q team could think we would solve it with the majority of us being memefags and rather graphically oriented (all good with that, no problem), but so few of the analytical/technical/crypto-familiar kind ….

>>2179128

Not giving up, meaning to say I'll sure stay tuned and will help where I can!

Didn't spend all the time for in the end giving up to the mofos possibly trying to mislead/distract us (and even worse).

…and also wouldn't even exclude the possibility that Q team had some part in misleading/distracting (as this is war) ….

Just saying that until I see a clear & consistent path to decipher it, I wouldn't wanna like to be (one out of let's say five) continuing chasing (possible) red herrings ….

With POTUS on his way back home, and an interview w/ Hannity scheduled later tonight, I'd expect more tweets to come for this day. Nonetheless, here's an updated version of the clockfags' clock (containing the # posts/tweets), and also the simpler version.

In case it would make things easier finding/verifying tweets & timestamps, I am also posting a PDF (110 pages) containing all tweets by realDonaldTrump in a table going back to Sep 2017. Times therein are EST (GMT-5), some deleted tweets are missing, some are in there – to see deleted tweets, one can always cross-check for example:

factba.se/topic/deleted-tweets

>>2186363

Awake, and in the classroom since 9 and school started …. reviewing.

>>2186638

trumptwitterarchive got it, and it's in the PDF. Times in >>2186516 are EDT again, but we've got that correction from @POTUS_schedule yesterday ;)

>>2186866

Thanks for asking. As the time of typing this, in LA it is 08:26 (EDT), or 15:26 GMT

www.timeanddate.com/worldclock/usa/los-angeles

With @Jack being at the helm, I wouldn't even exclude fuckery on his part … double-checking for consistency in accounting for DST at trumptwitterarchive & twitter.

>>2186965

Meant to say "08:26 (PDT)", instead of "08:26 (EDT)"

>>2186900

Here's what I'm seeing:

Last tweet (pic2, "_scr" is screenshot from twitter), was 07:39 a.m. PDT.

TrumpTwitterArchive has it 14:39 GMT, making it 09:39 EST (GMT-5) or 10:39 EDT (GMT-4, pic1).

The table created from trumptwitterarchive also has it 09:39 (EST, >>2186833 ).

Deleted tweet is from 12:59:36 (GMT), making it (GMT-5) 07:59:36 EST or 08:59:36 in EDT.

If all of the above is correct, and if you are seeing it 08:39 for the last tweet & 08:59 for the deleted one, then my guess is that twitter automatically accounts for DST, no matter what the setting. But I do not use twitter w/ user account, so I have little idea about the time settings there.

Can you set (as time settings in your twitter) EST & EDT separately, or is there only an option for "EST" ?

>>2187190

*if you are seeing 10:39 for the last tweet & 08:59 for the deleted one

>>2187189

10/4. That's what I see as well: Times are correct but they are EDT instead of EST.

>>2187292

Pic3 should confirm it: Time is "Eastern Time" which usually means EST & EDT, depending on calendar date and if DST applies or not.

So if that's the twitter settings you got, then currently & until Sun, 4 Nov, 02:00 (EDT) you will be seeing timestamps in EDT.

www.timeanddate.com/time/zone/usa/new-york

>>2186833

Reposting the PDF, as I had some trouble substituting a couple of HTML characters (dollar signs, ampersands etc).

Flags are still not converted correctly – but I think I'll spare myself the trouble ….

Will update the table regularly for those using EST, as the current assumption still is to look at Q's timestamps discarding daylight saving (someone get rid of silly daylight saving – confuses me all the time … lol).

>>2187288

"The Martian" is running here, while I am working on the clock, as usual. Little trouble here reading/converting hex to just about anything …

Could you (apart from random chars) give me one example, so I can see where this goes, that this approach makes sense, and that you've got a point?

>>2188028

Full charset result (hex2asc) would be:

eS}x§ªú¥v[q»¼

reversed (i.e. "F8 CB BB 17 B5 67 5A AF AA 7A 87 D7 35 56"):

øË»µgZ¯ªz×5V

>>2191326

>Take a look

I'm still not seeing much … but I might be looking at it the wrong way, or not intensly enough.

>because I know where its going already

Feel like explaining what you see already, and where this is going?

>>2191326

Since this is not the general, I'll try and be gentle a bit, but here's a couple of things:

1.) Except Q Army (ID: 9bb751) and you (ID 95d723), nobody uses bold/red in this thread

2.) You use words like "diligently" & "breakthrough" and appear pretty sure that you know what's going on with the clock. "Diligently" has only been used by one other ID in this thread.

3.) Above point even though your previous approaches, e.g. >>2167084 or >>2181206 as far as I can see, have little to do with anything about hexadecimal. And all of us around here have a more or less consistent approach, and all of us try to keep it low-key since we all don't know, trying our best figuring it out.

4.) Now you're even so sure that you've "broken the code", that we should "stay tuned", and also learn that this is the 2nd most exciting moment in your life.

5.) In your current approach, you sort timestamps by time (incl. mentions) – starting with the earliest, which would lead to all hour-values starting with the same hex value in your "-:-:-" notation, when we take for example date 20-Nov-2017, where we had seven posts at the 3rd hour.

6.) You forgot the "F" value for 17:19:42 in your graphic >>2191326 , as minutes correspond to the [:19] marker for 10/28 according to your system.

Now, I really don't know who you are and what's your intentions. I am not a Computer Scientist, as you called for this morning, but it is still not much of a difficulty for me to figure out what you're doing there, and automate it.

Thus, even though I am highly suspicious, but generous nonetheless and always try to be nice & helpful, here's a pastebin with all the hexcode you ever could want, in the same notation as you demonstrated:

pastebin.com/X8HD63sP

Didn't cost me much of anything – so no worries (or happies in case you're an agent) – and it's nothing but a nice exercise, even though I still doubt it'll go anywhere.

So maybe now you could share with us some insight and explain where this goes in your opinion, or get lost (well, that's my opinion due to the loudness you had to announce your "breakthrough" with).

>>2193217

>Do you want to help or do you want me to get lost?

I thought I made clear that I did not like the loudness you announced your "breakthrough" with.

>Show me something fellow Anon

Lol. Don't need to show nothing to nobody, young man.

How about you take some time and go over the list, verifying if I understood your "breakthrough" correctly, if there are bugs or errors etc.

The list should have spared you a lot of work & time, as far as I can see – so why not use the time it saves you to show us that it goes anywhere?

>>2193480

Not sure what you compared or spot checked, but seeing your pic >>2193284 and simply comparing your results to the pastebin, shows that for Jan 26 & 05:11:26 + 05:46:48 you get "C", while the pastebin shows "4".

That is, of course, because of the assumption that for every calendar day, the black line in your pic marks the day itself (corresponding to the 0 value in hex), and the other lines will arrange accordingly in clockwise direction, and so will the hex values that go with them.

For Jan 26 ([:50]) for example, [:51] will correspond to "1", [:55] to "2" … etc, and [:49] to "F" – that's why hour "05:" gets hexvalue "4" in the pastebin.

This is one example for what I mean with being low-key and still trying to be accurate and careful (as good as we can) with what we do ….

@realDonaldTrump tweets on days w/o Q posts can be added easily, if you think it's necessary …. still not much use if there'd be errors on my side in understanding your idea.

>>2194001

No worries. I will get you your hex code as you wanted, since it doesn't involve much time or work. Still, it'll have to wait until tomorrow, as I am calling it a day for now. Also, I am much more trying to follow the "master clockfag's" ideas, as these seem to be much more along "Q-typical" lines.

>>2193217

Raw output is in pastebin.com/1PE6301h

It now also contains @realDonaldTrump tweets for days w/o a Q post

With dates/times removed that have no hexValues ("-:-:-"), and sorted all by date & time, the result looks like this:

pastebin.com/NracEeQ5

You asked for two columns, and the pastebin has three – but I think you can work with that just the same, and I wanted to preserve dates & times.

Also cleaned out UNIX seconds after sorting – they are the best way to sort/do math with timestamps, and dates/times of the form "[DD-Mon-YYYY HH:MM:SS]" are dates from Q posts, while dates/times of the form "[YYYY-mm-dd HH:MM:SS]" come from tweets. Not sure if that's of relevance for you ….

It's always good to double-check (by an independent party) – so if you did some more manual work yesterday (admire your hard work, patience & persistence), then it'd be useful to check results at least in some spots.

There's also the issue of deleted tweets. Not sure how you were planning to deal with that ….

If all is correct & sorted as you imagined, it's just another simple one-liner in the CLI to convert all hex to ascii.

>>2196846

>>2198470

Double-checked some of it myself, and found a bug in computing the "0" hexValue marker for days w/o Q posts (duh!).

I apologize for this, and have corrected it – here's the new output for raw results, as they come out:

pastebin.com/dgDuhA2x

Sorted by time and cleaned:

pastebin.com/TMfN1ybs

For convenience, here are the hexValues as concatenated in pairs to give a maxValue of 255 (extended ascii charset, not sure if done in accordance with your idea:

pastebin.com/WErk0wai

>>2200232

You mean like this?

(1st & last ten lines):

00:01:22 -:4:-

00:02:16 -:-:2

00:02:52 0:-:-

00:02:58 9:-:7

00:03:28 -:A:0

00:04:10 -:6:9

00:04:38 -:-:E

00:05:18 9:-:-

00:05:38 -:-:C

00:05:51 9:-:-

. . .

. . .

23:55:21 -:-:3

23:55:41 -:3:-

23:56:48 -:8:-

23:56:55 E:-:-

23:57:15 0:-:-

23:57:23 F:-:F

23:57:40 -:-:3

23:57:41 -:6:-

23:58:50 C:5:-

23:59:18 0:-:E

>>2200421

Alright then, the pastebin with solely times & hexValues: pastebin.com/nWANdkE6

HexValues only, arranged in pairs as before: pastebin.com/0JaHcrpA

>>2200552

Not so awesome … all just curiosity and laziness. lol. Thanks nonetheless, I'll keep the scripts for later use.

If this is something, then congratulations to you, however, as this was your "breakthrough" ;)

>>2200930

Thanks. You don't think I'm doing all this and not checking what is (or could be) in the hexCode, right? ;)

Curious, and well aware of various archiving formats & their file signatures … so let's see. I'll certainly keep an eye on it, and will re-post the sequence of hexValues on a regular basis.

>>2213359

Honestly, esp. around here, nobody cares if you think the clock is craziness or stupid or faggotry. Deal with it.

As with all graphs, maps & plots the clock is a model to visualize a (more or less) complex problem, and through that make it easier for idiots like us to see what's going on with dates versus times versus markers and their symmetry to each other. Also there could have been the possibility of patterns emerging from the blue dots and as they arrange around the clock as Q posts accumulate.

If you're so smart to do all that in your head/imagination, then more power to you, and indeed you wouldn't need the craziness that the clock obviously is to you. This all, of course, apart from the fact that Q mentioned the word clock 15 times in his posts.

Other than that, this thread is dedicated to researching the clock. Nobody ever asked you to believe in what is done here, or there with respect to the clock.

Hey shitheads !,

have at it … enjoy ! LOL!