f generation is currently down (9403 error: Invalid token)

[frozenpandaman]

It seems that the imink API, used by s3s, is currently down due to Nintendo updating the f generation method (!)

Example of f generated by Nintendo: 9aee4e7dbf18b41a006a70fed8437e1d5fed17828a053157b9a0b9ab5dae8002bb6d78ad49cc645c42e97dd7d445527c34ba302c1772ced73099e0afff00e533b5311b6ff7████ (142–144 characters)

Example of f generated by imink API + s3s: e3eb429ef99d4b0be3b8dc7667bbcf422a3ba22383392292b2cc8fd94cd74b53b6704fe2cee3e8b0c401517e02████ (94 characters)

Tokens needed for s3s to work can still be manually input by following the mitmproxy instructions.

Alternatively, projects using the 2.4.0 version of the NSO still work, e.g. nxapi-znca-api. You can use this endpoint by changing the value of the f_gen key in your config.txt from https://api.imink.app/f (default) to https://nxapi-znca-api.fancy.org.uk/api/znca/f.

---

EDIT: @JoneWang has let me know that requests to the imink API will be redirected to @samuelthomas2774's alternative nxapi znca API server for the time being, which is based on the most up-to-date version of the NSO app and thus still works. No change to s3s or config.txt is required at the moment to keep automatic token generation/login functioning. The fix was easier than expected so this didn't even need to happen!

[frozenpandaman]

The imink API has now been updated and everything works normally again (nice!)