>>210532

USAI has undergone a lot of reconstruction with the advent of digital comm. I was 05H - morse intercept. That MOS is no more; its task has now been merged into 98G which is (oddly) linguist or voice intercept. By the early 80's, the shift was just beginning to occur. Huge operations, such as the Field Station I was at, are now shut down and abandoned. Kinda sad to look at if you were part of any of those.

>>210537

Weren't there a whole slew of those over a few year period in the 2000's?

>>210611

You are clearly not the average anon.

More than that, we don't need to know.

>>210611

I just uploaded a text file with headers only from every Q message. Easier to work with for this.

http:// www.enigma-q.com/headers.txt

Image here is just to get people's attention.

Hex goes 0 - 9 then A - F to represent 10 - 15.

I doubt the ID would be part of the equation since the user can't control that - it's based on IP address. Still, at one point Q mentioned the ability to use random IP addresses so we would need to check that line of thinking just to be sure.

Trying out this clock decoding, I just hit one SEC web site (.onion) that says access denied. On the right track?

Working with this clock thing … trying all kinds of translations … values against a text string that runs 0-9 then A-Z, a second string that runs A-Z then 0-9; h:m:s modulo 15, or each converted to degrees; tried hour * 1.5 (360 degrees / 24 hours = 15 degrees per hour), minute * .6 (360 degrees / 60 minutes = 6 degrees / minute) and seconds the same as minutes.

Tried running h:m:s:h:m:s etc. as onion addresses, both translations. As search terms these strings were returning interesting results more often than not - domain name checking, Cecret_Lake_Panorama_Albion_Basin_Alta_Utah_July_2009, but nothing concrete.

Now working with time between messages. In seconds, in minutes, etc.

>>210691

Ditty boppers rule! The old AN/FLR-9 … abandoned but still standing.