>>10319226

>Well I offered…

Can't remember having heard of "the SpuriousSpace/CrumbLineLengths decode" yet.

Don't be mad about late answers around here – just post away and clockfags will have a look at it once they're around.

Usually, and if it makes sense, they'll also comment on it, ask questions or pick things up and develop them further.

I'm curious, of course, so I would appreciate if you took the time to post some details about the decode you mentioned. Thanks!

>>10638382

>>10634979

CMCF here, the "usual baker".

Still travelling as well and still have no possibility of creating the usual clocks and the tweet PDF.

But will be able to use QClockView for updated blanks as done by SOCF so far.

Have the dough for #10 ready and could bake a new clock bread probably by early morning tomorrow.

Will check posts after those notes were posted to add posts in case necessary, and re-post updated notes before baking the new one.

Safe travels SOCF!