>>2221272

Clock 101:

5th point is probably incorrect, or I don't understand what you're trying to say

6th point, so far, is a working hypothesis – should probably not be in the 101

However, shared timestamp probably should go into the 101, as they're related to symmetry/mirroring of the markers

How to read the clock (Primary):

Good so far, but I'd also include that all shared markers should be checked (not just the reflection)

Secondary is a bit unclear/incomplete is my guess – this may be because it's work in progress, or because I haven't 100% understood all of it completely (yet).

>>2221163

Don't think anyone has anything against you working on the clock or sharing your ideas. However, so far these have been ideas only and you haven't come up with more substantiated indications that indeed this kind of "time-lapse" cryptography might have to be applied (or even looked into at a deeper level).

By technical arguments (and I for one and for now also see it that way), the anon >>2218058 is not wrong. If your only argument is that it takes as long to decrypt as to encrypt, then – indeed – all work here would be futile (for most parts), and we'd just have to wait.

Again, your idea probably made it to the notables for not to be excluded as a possibility – but so far it's lacking any further evidence/indications.

Also, please spare us things like "I win!" – it says that you haven't understood what you yourself are doing (as – stated above – I don't see strong enough evidence for your idea), and it also shows that you haven't understood what Q said: We all are winning, or none of us!

Further, if you need something, it'd be appreciated if you first tried it yourself, before asking other anons for help (in a possibly futile idea), and with that (if they want to be helpful) maybe distract them from their work.

If you have/give examples, that your ideas are working, or even explain your ideas so that they are plausible (or not) to some of us, I am sure, given the case, anons will do all they can to help.

Finally, >>2220529 – we should all be around long enough to know that the spreadsheet exists (maybe even long enough to know who helped you with the timestamps in the beginning).

It's also in the dough of every bread in the general. and most of us likely appreciate your work.

However, I'd really appreciate if you'd not advertise it around here repeatly (and that's where the emphasis goes). You've done it in the last bread, and also here by now at least three times ! What's your purpose in doing that? We all know if we need it or not for our work, and also are capable of telling fellow clockfags about its existence in the unlikely case they're unaware.

Re-posting here from the General:

Someone linked the page reputationhijacking.com/ , which contained a timer, that had expired tonight >>2224983

The page, in its source code, contained a commented line (not visible online):

"W3htbG1qdyB1Z2Vla10gdXNqanEgeWdndiBbaHpza3cgM10gZ2h3anNsYWdmIGJta2xhdXcg"

which decodes (base64) to:

"[xmlmjw ugeek] usjjq yggv [hzskw 3] ghwjslagf bmklauw" , which in turn (rotCipher w/ rot=8) decodes to:

"[future comms] carry good [phase 3] operation justice"

It may be clock-related, since it had been speculated (early in the Q-Clock's life) that the "phases" mentioned by Q could be (approx.) 75 days apart (pic).

If this assumption is valid, then expiration of the countdown could mean two things:

Either "pre_stage" of phase 3 is over, and now "phase 3" starts, or "phase 3" is over and "phase 4" started/will start (if there is any at all).

>>2229502

Morning y'all. Yes can be decoded. Just fell asleep yesterday so I didn't try all.

First, "R=18" (the rotCipher/CaesarianShift) can be both directions (the rotation). Webpage I use for that uses R=8 (decoding), which would correspond to R=18 (encoding), as 8+18=26 (the #letters in latin)

The part:

N0Q1uYMpQJSUs21kt10ETcSpQM9quXWeQJScsXMwvH0BLYAcO3E0PNucZYEcP195UHgHtdMwt3IyQ2LxQXcpO3bETcSpQM9quXWeQJSaPOSwvH0BN09lLdMyQYcu

by using Rot=9/17 decodes to

W0Z1dHVyZSBDb21tc10NClByZV9zdGFnZSBlbGVfeQ0KUHJlX3N0YWdlIHNlY195DQpQcmVfc3RhZ2UgZGlyX3kNClByZV9zdGFnZSBjYXBfeQ0KW09uUmVhZHld

which in turn using base64 decodes to:

[Future Comms]

Pre_stage ele_y

Pre_stage sec_y

Pre_stage dir_y

Pre_stage cap_y

That's with leaving out the last three letters ("UHf") – checking if that's anything separately ….

Here's a quick update for clock, tweets & hexCodes.

Results (times & hex + hex only):

pastebin.com/pVGEmF7w – Hex only

pastebin.com/gA8aQJjW – Times & Code

Also an update/addendum to the post re. reputationhijacking.com above >>2226210

Looks like the webpage had another code included which I had not noticed/overlooked:

Via reputationhijacking.com/securedrop.html one could come to: reputationhijacking.com/wikileaks.html, if one would decode (base64) the string L3dpa2lsZWFrcy5odG1s at the end.

L3dpa2lsZWFrcy5odG1s → /wikileaks.html

There, one can find an image of JA (2nd pic) and:

Without Wikileaks none of this could have happened.

Why did Patriots attack the librarian of a movement?

What is the purpose of the directed attacks on the psyop?

We are pushing for the ability of have a Free Press.

POTUS speaks on wikileaks well in the speeches.

The Proof will be more than anyone can understand.

disinformation is nessicary to show you the players in the FAKE NEWS Movement.

Find your inner light and help end the silence.

We will have silence no more.

WWG1WGA

#nomore

#Unity4j

#Unity4j leads (via twitter.com/Unity4J) to a live stream which will start 6 p.m. (GMT-5):

www.youtube.com/watch?v=AdzBFeWXSxY

(not sure about the timezone – youtube on my machine says 11 p.m. after for a sec showing "6 p.m. GMT-5"). So could also be 7 p.m. (EDT)

>>2229702

Thought so too, and have checked securedrop.org with various combinations of "securedrop.org/directory/UHf" , "fHU", "Fhu" and others – will keep on checking/thinking. Haven't tried getting the cloning the github yet.

>>2230724

The two Codes were on the webpage posted about in the General yesterday >>2224983

You would find them in the HTML source code (on firefox right-click and select "View Page Source")

>>2235765

You mean as simple as this:

00 → 95

01 → 89

02 → 33

03 → 22

04 → 30

05 → 91

06 → 134

07 → 146

08 → 135

09 → 92

10 → 96

11 → 116

12 → 121

13 → 121

14 → 100

15 → 139

16 → 141

17 → 135

18 → 145

19 → 125

20 → 136

21 → 143

22 → 137

23 → 135

?

>>2236945

Well, I counted all lines starting with "00", then "01", etc in the clean version of codes that only contains times and codes as posted in >>2230779

The pastebin is sorted by time and has linenumbers – so it shouldn't be too hard checking the results

for 23 I see lines from 2523 – 2657, making it 135 lines …

That's why I was a bit unsure if it really was this simple what you asked for.

>>2236853

These are interesting (as all of your work). Had to step back a bit and let things sink in going over all the proofs (again and again), also building tools that would make it easier for me.

Didn't want to do it like the girl in the movie (pic), making circles all around things I don't understand … lol

Will probably be able to sum things up a bit by tomorrow, and maybe ask some questions too.

Re: Matthew 7:7 – it's not easy to ask questions when one hasn't even understood what to ask exactly, or where to start … ;)

>>2241591

Thank you – much appreciated as always.

The #1776 was a good one (double meaning), as it also was posted as the 7th post/6th reply in bread #1776 (upper right corner in pic).

>>2241956

Thanks. yw.

As for Q confirming the clock: I think he did already – several times, indirectly and also anonymously.

For all other purposes, I believe there's a reason for him not to confirm it directly and w/ trip, at least not until we've understood it (and can prove its value & correct use) – but that's good enough for me.

So, yes, posting at :47 marker would be another indirect confirmation adding to the (im)probability calculation – somewhat similar to 06/03 when posting at 14:58.

>>2242520

Not sure if this is what you mean: But (see >>2225799 ) there are three (or two when seeing the first pic as a subset of the second) theories as to what the "mirror" is, i.e. the symmetry axis (or mirror axis).

Personally, I believe both should be considered.

What you are doing is pic1 (in above post), meaning you take the reverse. That is, you mirror (or reverse) marker [:39] onto marker [:09].

If [:25] → [:55] is seen as the mirror axis, then [:39] is 14 mins away from [:25], and your mirror line should thus be at [:11], which also is 14 mins away from [:25].

But I really don't know if this is what you're asking.

>>2242940

Ah, I see now what you mean. Also posted here, above in >>2241591

Obviously, the anon reversed (i.e. 180 deg) the "observation ray" from [:39] to [:09].

Can't tell you what he meant with "confirmation of the :25/:55 mirror line" though.

When assuming [:25] → [:55] is the only valid mirror line, then there's only a single case were the reverse (180 deg) at the same time is the mirror: for the pair [:40] & [:10].

If it wasn't in error, then maybe it'll be explained to us when he/she posts here the next time.

>>2243503

Thank you, poor farmer! Lol. – Now the "cluckfag" thing makes more sense too.

… and also for the work & for confirming the error!

However, it wasn't that bad posting the two, as indeed it could be seen as some kind of confirmation – just not of the mirror line at :25/:55, but of the "reverse mirror". Personally, I wouldn't be too fixed on any single one of the theories pictured in >>2225799

If I am not mis-remembering, the reverse mirror theory has pretty often already shown some validity. Godspeed.

Currently, the most plausible results I see in the work of our "master clockfag", using shared timestamps, connecting tweets & Q posts and also introducing the concept of "unlocking" (or "locked" & "unlocked" states).

These things all relate plausibly to stuff Q posted, incl. Bible verses, the [2] Q Chapters, "here" & "there" etc …

I'll try and describe what I observe – so please note that I have the gif ("you wrote so much text", lol ;) ) … just trying to make it understood and reproducible beyond images only.

Part I:

This is getting quite complex, and as I said many times, I'm kind of stupid getting all things together quickly enough, and this with POTUS & Q team probably getting impatient …. kek!

I'm a language guy, most generally speaking, and I don't care which language. Can also be math, physics, computers or any other system (with reproducible rules) – but when complex/difficult, it takes time to learn/observe. A lot of practice/repetition & some kind of "teacher" help even more. Merely trying to understand & repeat what has been done in the pics above. I have no idea if I got it right, or even if that's how the clock should be used, but here's what I see:

"News (in all forms) unlocks the map.", and also "Future unlocks past."

For sake of simplicity I'll assume real time-travel is unknown to man (maybe impossible). So in order to (sometimes by exact words) "point" – in a contextual manner – to a certain Q post in the past at a certain time, some news outlets cooperate with Q team/POTUS or are otherwise usable/prone to publish specific content at specific times, so that the correct connections can be made on the Q-Clock.

Going over many of the proofs posted here, it's safe to assume Drudge is one of these outlets, possibly FOX as well, and others. It's clear that also POTUS's tweets are one of these news sources.

>>2228579

Taking pic2 as an example for starters (re-posted here as pic1), here's what I gather so far:

Logically, "here" is always the present. To "unlock" sth being an active process, you can "unlock" sth from the past, but it'd be impossible to "unlock" sth in the past. Similarly for the future.

So, ("Today", the present, center in pic) what did POTUS' (brilliant) tweet from 07/16, 04:29 p.m. EDT "unlock"?

First, tweets & Q posts can be connected by deltas (i.e. timestamps), minute markers, and also context.

Since we should "START HERE.", we could gather all Q posts with a minute marker of "[:41]" from the "Here" timespan (see >>2102778 , pic1), which lasts 03/23 thru 07/04.

I found a single Q post which directly (by topic) connects to above tweet from 07/16 (pic2, "Peace through strength.").

Pic1 shows another Q post with Pen #5 ( >>2232057 ). The pen points to the exact same day it was posted (i.e. 05/19).

It's still a bit unclear for me, why this post is in pic1 (05/19 marker is [:43], and by topic only distantly connected), but the tweet referenced therein is from 05:27 p.m. – maybe it's the Delta to [:41] of 14 mins, which reversed is 41 again, or (more likely) it's because our clock is two days slow.

Another post (pic3) is of rather technical nature ("8ch risk"), and can probably be discarded despite containing the word "risk".

Part II:

07/16 (POTUS-Putin tweet, pic1, last post) goes with marker [41], belonging to the quadruple of "shared" markers: [11][19][41][49]. It's notable, that the 7th word from the start, and the 7th word backwards are both "risk".

I have checked all posts with these timestamps (in minutes), and didn't find any that connects directly to the tweet, except the "Peace through strength" mentioned in Part I above, and one mentioning "8ch risk".

It may be, however, that POTUS' tweet "unlocked" some past crumbs, as mentioned in some of the posts above.

It appears as if that process of "unlocking" introduces other valid markers, which might have to be checked. Following what's been posted in >>2236853 , it would appear as if "unlocking" results from a rotation by 15 mins (and re-ordering of the timestamps. This process is demonstrated in a small movie ("unlock.mp4"). If this is correct, then marker/timestamps [04][26][34] & [56] would also have to be checked for possible Q posts that relate to the tweet.

Checking all these, one finds three additional posts with minutes or seconds being [04] and [34] (pic 1–4).

Part III:

In lots of the "master clockfag's" images, certain words are marked, sometimes complete lines.

Following the work above (and from last bread) of extracting last words from Q posts, it appears as if sometimes last lines are extracted, sometimes it's a certain linecount, sometimes words are counted/marked.

This counting of lines/words can be done forward & backwards, likely discarding Q's signature (and other signature, like possibly movie signatures).

From the "risk" posts above, they also seem to be corresponding to the markers in use.

As an example, in the "Games of RISK" post, it is in the 11th line counting backwards (marker [11]), and "RISK" is the 19th word in that line.

"[risk] of conspiracy" is the 41st line backwards (discarding signatures Q & Geronimo). In post 616618 (last pic in Part II), "Risk of 'conspiracy'" is in the 19th line counting forward. This certainly requires a little more counting, and also being clear, for example how posts mentioned by Q should be counted (linewise).

To – for now – only briefly mention "Past" & "Future": Similar concepts as described in Part I & II, would likely apply to Past & Future (possibly in some simpler form). It is important to note (see e.g. >>2228579 ), that the original set of shared markers, in the chosen case [11][19][41] & [49], with [41] being the referring one, change to:

For Past: [12][18][42] & [48] – by adding 1 to the referring marker [41]

Future: [09][21][39] & [51] – by subtracting 2 from the referring marker [41]

Altogether, this seems quite a mess on a first look – and it's not unlikely that I see/describe things too complicated.

However, having looked at many of these images, and still not understood everything, it seems to me as if it would be less complicated/convoluted than it seems. There appears to be fixed principle/procedure behind it, which, when understood, is "only" a lot of repetitive work to apply to all Q posts & tweets.

Apart from the possible contextual relation of tweets & posts, many of the steps can be automized, or tools build that make searching/scanning for context easier.

>>2249139

Thank you for that – I did overlook it, and it was in the copy of the page that I made back then (and not added later).

The phrase seemed too much as if I'd read it before though – and lo & behold, it was in #2811, with an image of the Captain.

Thanks again.

>>2247021

Noticed that too in the previous breads in the General.

Looked to me like the guy was jerking off on his numberfagging primarily, and his 8chan slang about almonds & that it's almost impossible to grasp (except for him of course).

Blurred out most parts of his images, mumbled about geniusses (sic), zigzagging through time & that he will not spill the beans before [monday].

Also he was making random use of arbitrary parts of timestamps (e.g. using "7:03" from "17:03") and including the numbering on qanon.pub to make his connections (when there's indications qanon.pub is not 100% accurate, and could even be associated with PAnon), and also attacked anons expressing doubts about his work –

So for me as of now just another bragging mofo who's using parts of our work here while not sharing his. Needs to point out he's dutch too – so just exactly the kind of guy we like around here …. lol.

>>2255085

Go dig yourself, or go fuck yourself – or better both! Here's one tippy-top link for you to start with in case you decide to dig before having fun: www.slideserve.com/johana/john-frum-the-cargo-cult

>>2254991

>>2255933

It had been suggested to extract Q posts with any arbitrary word. >>2032170

Well, I have build a small tool for that – still working on rendering it into the right format (PDF or PNG) – still not working out as I want it to.

But I could sit down right now and try to finish it, if this would help.

>>2256501

Yep. Pen #1 was posted 12/12 & Pen #4 was posted 05/10. The other three point to the day they were posted.

>>2253797

You've probably found it out by now. In case not: (pics)

Happened b/w 1822 & 1823. Clock threads 1 & 2 were in the same line, baker cleaned out inactive posts – clock thread #2 probably was cleaned away inadvertently while removing link to clock thread #1.

Posting updated clocks, and PDF with tweets by @realDonaldTrump

Catching up on the other happenings …

>>2260486

Just quick w/o touching on the other things:

I'm impressed – this is one beautiful masterpiece of clockwork from Geneva!

>>2268112

Looks like POTUS telling us to continue winding (and working).

Since I consider it relevant, and don't believe in coincidences of this kind, esp. with the song in the background, I have cut out the part (until the end of the song), for offline use/archiving.

God bless POTUS & Q Team!

I'm proud to be part of this!

>>2269988

If you look further up >>2263446

then the 180 deg mirror of today ([:49]) is at [:19].

You got the 02/24 one correct. The other day is 04/25 (instead of the "ANTIFA" day 04/26 ← that one is at [:20])

>>2269988

Correction, sorry: The ANTIFA post was 04/25, so it was probably just a typo when you wrote "4/26"

>>2271623

Thanks for re-posting. Seen it starting in 2859 & in 2860 again, with question

"What are they trying to tell you?"

Strange way of asking that question, weird filename too …. Will certainly have a cautious look at it. ;)

For the Sea to shining sea: Found 5 occurrences of "shining" – two with "light", the other three with "sea".

Posting final (for today) update for clockfag's clock & @realDonaldTrump tweets – we're at 1700 Q posts in the three timezones archive (1692 at qanon.pub).

T'was a fine day today, fellow clockfags! A pleasant Good Night to all of you! Will be back to regular clockfagging tomorrow.