>>19426

>>19465

>>19411

Believe whatever you want, but you haven't found [0]. Tweet was 23:15, post was 22:15

On TrumpTwitterArchive, try exporting tweets to CSV-format, and you should get the original GMT timestamp (see pics).

>>19514

If that's how the rules are (and hours don't count) then you'd be correct. With the confirmed markers so far, however, the hour was always the same.

>>19516

True. Would like the [0] to be found too, but as long as hours count, numbers (and the HTML source) speak the truth.

>>19525

>>19560

I know little about what Q meant, but judging by clocks, and 04:10:20 and all, I should think a clock has more than a minute hand and hours (maybe even seconds in some cases) might count.

>>19560

>>19580

It was meant re. those markers, which was addressed today, I believe.

This pic >>18138 is a repost from #21. So maybe we'd wind clock according to the markers we find.

>>19619

I know it's not the same hour & minute, and checked it. All other markers had same hour & minute – so I assume hours count, as in real clocks. Thus seconded.

>>19649

Funny how things happen, thought of Vignere today as well, but didn't get me anywhere.

You can try it yourself here: >rumkin.com/tools/cipher/vigenere.php

the guys pass was "patriot".

>>19737

Thank you. Also I noticed some threads have now less than 751 posts and in some cases this number still keeps getting lower, eg #20, #18, #14. Any ideas as to who and/or why ?

>>19742

ad hominem ? hehe. wrong place then 8ch for you, I should think, faggot.

>>19765

thanks. If possible, maybe we should lock threads after they reach 751.

>>19779

All the better (if related). We've got "double meanings". I meant the clock/keystone from there >>18138 re 04:10:20

>>19822

Like so you mean ?