I found the needle in the haystack is exactly what happened.
It only took 55 years.
I even think if this cipher was referred to as the Mount Diablo code rather than Z32, it would have been solved sooner.
The name itself is a further hint to the origin point of the projection, as if the big crosshair wasn’t enough.
How obvious did he have to make it?
It was the problem with this cipher, people did their own thing with it, like renaming it to Z32. He called it the Mount Diablo code, and that is what it should have been referred to as.
When they interpreted radians as being used correctly, they ignore the clock hours hint drawn around the origin point.
When you use radial lines at clock hour positions you land at the triangle I found.
His post script hint actually contains multiple hints, in only a few words. He names the cipher after the origin point, he gives away critical words in the plaintext, and he gives the instructions for the projection step.
It is very obvious he gave the post script hint knowing it would be necessary to solve the Mount Diablo code. And so I’ve solved it in December 2025 using Python.
The fact that experts rebranded the Mount Diablo code to Z32 is a subtle naming error on their end. It shows they were more interested in the length of the cipher, rather than the included context, and the authors own naming conventions, which was itself a further clue.
While a small number of people have performed incredible mental gymnastics to “debunk” my personally confirmed solution from all angles, my position remains the same and hasn’t changed since December.
I had asked for someone to orthorectify (correctly) the ’69 or ’70 images from USGS of the specific region I have located. This is very hard to do the right way, and so that hasn’t happened.
If you call the Mount Diablo code impossible to solve, then it is impossible to solve.
If you call it possible to solve and follow all of the rules of the system then you land at the triangle discovered by David Stampher in December 2025 using Python.
And by the way these forums are a very informal setting, and so I am being looser in my communication style here.
In other environments I am much more friendly. In fact, that was very much my initial approach for months.
So there will be typos here, grammar errors, brain farts. I am not really editing myself and just still waiting for the triangle to be scanned. I like some of the GIF’s I’ve shared for the people.
And others can disagree but natural origin theory, watering hole theory, annoy me and that is just the way it is. I really haven’t heard much else besides that kind of thing.
They can even disagree if it gets scanned and I was right the entire time. “High degree of confidence” is what I will go with, nothing wrong with that given the landmark. 99.9% certain leaves the door open, it is a matter of probability. Others can say 0% chance, it is a matter of opinion.
You can expect the guy that produced the 24 page whitepaper arguing in favor of IN THREE AND THREE EIGHTHS RADIANS TEN being the solution to the Mount Diablo code will continue to do so until the GPR step happens. As my next one is longer/better. Still going strong.
Focus has relatively returned compared to the Valley of Despair brief period after getting censored. Better REM sleep ect. Enough to be able to continue.
And by the way these forums are a very informal setting, and so I am being looser in my communication style here.
In other environments I am much more friendly. In fact, that was very much my initial approach for months.
My previous friendliness and respect even towards some initial dissenters (I also had some supporters) was unfortunately censored due to a pointless ban. Dissenters were initially my friends, trying to help me work through this. It was collaborative initially. But after seeing all of the angles people will generate, I realize it is a never ending battle. So long as they reject the idea that Zodiac constructed the triangle, my personally confirmed solution is wrong.
I am betting that Zodiac constructed that triangle landmark by LHR.