Preserving the whole PSN identifier

An account ID can be larger than a signed 64-bit integer. The September 14 PSN finder update addressed a subtle consequence: casting Sony's returned value directly to an integer could clamp a large ID before we ever encoded it.

The correction kept large JSON integers as strings and converted the decimal value into the required eight-byte little-endian representation without that signed-integer assumption. The implementation used GMP when available, BCMath as another path and a manual fallback. The work record includes comparison tests against the expected packed representation.

That's a small amount of code with a very practical effect. A user shouldn't have to wonder whether the result is wrong because their account happens to fall on one side of a numeric boundary. The conversion needs to preserve the complete value before Base64 encoding it.

The request limiter also moved from an unkeyed address-derived hash to a keyed HMAC with a persisted random secret and daily rotation. The deployment record checked that its storage directory was writable. Account-detail copy was revised to describe what wasn't retained, without pretending the service had no operational state at all.

The landing page and tool also received matching attribution to Chiaki's original work and corrected Sony-host wording. Updated desktop and mobile screenshots followed. The website record reports the revised files deployed and the expected public copy read back.

These checks establish the recorded conversion and deployment work, rather than a new authenticated PlayStation session performed for this article. The useful progress is clear: preserve the full identifier, explain the sign-in boundary accurately and keep the credits attached to the implementation that made the tool possible.