Anonymous ID: 16cb11 July 21, 2018, 4:08 a.m. No.2229709   🗄️.is 🔗kun   >>9891 >>9917 >>0183

>>2229595

Baker, re: Notables #2806, post >>2225964

The pic in >>2224983 had another long code shown, which I only managed to look at this morning.

"N0Q1uYMpQJSUs21kt10ETcSpQM9quXWeQJScsXM [...]"

 

Using a caesarian shift first (R=9/17), and leaving out the last three letter (UHf) it decodes to:

W0Z1dHVyZSBDb21tc10NClByZV9zdGFnZSBlbGVfeQ0KUHJlX3N0YWdlIHNlY195DQpQcmVfc3RhZ2UgZGlyX3kNClByZV9zdGFnZSBjYXBfeQ0KW09uUmVhZHld

 

which decodes (base64) to:

[Future Comms]

Pre_stage ele_y

Pre_stage sec_y

Pre_stage dir_y

Pre_stage cap_y

 

Checking "UHf", and what it could mean (apart from the obvious, i.e. UltraHighFrequency) ....

Anonymous ID: 16cb11 July 21, 2018, 5:22 a.m. No.2229944   🗄️.is 🔗kun   >>9984

>>2229891

Just as a side-note: Baker called me "Leafy" yesterday, when he put it in the Notables >>2226152

Not that it would matter to me very much to me, and hold our bakers in highest esteem, but he's wrong in case he was referring to aflb …. got nothing to do with that guy. Am just one of the clockfags around here.

Anonymous ID: 16cb11 July 21, 2018, 6:12 a.m. No.2230177   🗄️.is 🔗kun

>>2229934

Got it, and saved them. Thank you.

Someone around here a while back said sth like:

Imagine it would only need two weeks of training for anyone to be able to communicate w/o an electronic device …

Think it's very much related ….