Adding Yesterdays post about Prime Numbers in case some folk missed it
memory bloc 1728694800: PRIME
Value: 2136,279,841 – 1
Book 7. A prime number is one (which is) measured by a unit alone.
Memory compliance: 100%
Entry logged by:
System
edit: after 24 hours plus of failed calculator attempts, a new diagnostic log appeared
Edit: July 4th 2026
It seems that the calculator was for each Operator to find their Prime number and send it into System via Email. Since the Calculator automatically resolves to the nearest prime number of your mathemtical Sum, it was an aid for Operators to get a Prime number easy.
Operators were free to define their origin this way, be it a combination of birthdays or anniversaries via multiplacation and addition, their personal favourite numbers, their lotto numbers, the reasoning can be as vast and as unknown as the Operators thesmelves.
Upon emailing System, they would get a response saying that they were free to use this Prime as their OpID, or that it was already taken, and to try another.
They were a waking titan participant, but they could not find their username or login from then, it seems they may have chose to have their info purged during the changeover but not 100%
Their new join date to etarc for PSS is May 20th 2026.
Didnt they have a birthday recently? There was so many in the last week I forget who had one
They have our email addresses. Our IPs now. And they’re looking for someones birth date? Maybe PSS is actually just a scam Phishing event
The forum only asks for day and month, not year for birthday. Our joined date has the year. June and July are when most people joined for WT. Maybe their user name from WT had a number with it. That can make it hard to find if you don’t remember that number.
The flashing between two numbers behaviour changes if you enter 13 x 17, it shows 221 briefly then changes to 223 .. and settles at 223, no jumping back and forth as it did with 3 and 5. Nothing clever, but it is a behaviour change, maybe significant or not .. I am but a worm :).
The calculator works in two phases every time you press =:
Phase 1, local eval: The expression is evaluated in your browser using JavaScript’s eval(). This result appears instantly in the display.
Phase 2, server fetch: The calculator POSTs that value to admin-ajax.php?action=proc_z7k9. The server finds the nearest prime(s) to your result and returns them as JSON.
The display then updates based on the server response:
Single prime returned: If only one nearest prime exists (e.g., eval = 2073 → nearest prime = 2069), the display switches to that prime with a brief 0.6s RGB text-shadow animation. The number stays stable after that.
Two primes returned (tied distance): If the eval is exactly midway between two primes (e.g., eval = 133590, equidistant from 133583 and 133597), the response contains “or”. The display then alternates between both primes every second indefinitely, with a 0.4s glitch animation on each swap. This is the “bouncing” behavior.
Eval is already prime: The server returns the same number. The display shows it with the 0.6s animation but the number never changes - it’s a stable result from the start.
The glitch animation (rgbGlitch) always plays, creating the red/cyan text-shadows. The key difference is whether the display settles on one number (single prime) or keeps alternating forever (tied primes).
The server action proc_z7k9 simply returns the nearest prime(s), it doesn’t do anything else (on our receiving end). What’s happening server side to return it is a black box, and may be time gated (or gated by other things). The calculator seems to be purely about transforming values into their nearest prime via a remote lookup.
The numbers required to get there are going to be specific to @YourBasicMaths and we should allow them to solve it.
I have my suspicions on the solve and working (if it isn’t a private date), and offer them only if they get stuck.
It would be nice for Operators to respect that this is almost certainly for YourBasicMaths.
