Version 0.58.0

Your recovery list can now be stored on the storage network with your files, so your account code alone is enough to get them back.

The recovery list is the index that says which stored bytes are which file, and which key opens each one, and until now it lived in two places that can both end: your own disk, and our database. You can now have it stored on the storage network as well — it rides inside the same bundle as the files you upload, so there is no extra signature and no separate payment, and the amount you approve already includes it. With it there, the recovery program at github.com/needmoretruth/nmts-recovery finds your list from your account code: it derives your wallet address from the code, asks a public node what that wallet holds, and reads the list out of it, so nothing of NMTS has to still exist. ⛔ It is off unless you turn it on, because the storage is paid for from your own wallet to the Walrus storage network and NMTS receives none of it — the account screen states what it costs, what it buys, and the two cases it does not reach: paying with a browser-extension wallet or an imported private key, and files of 64 MiB or more, which are stored on their own.

The recovery program can now look your list up on the storage network by itself.

Run it with --find and it works from your account code alone: no saved file to hand over. It shows you the wallet addresses it is about to ask about before it asks, because those questions go to public services and you should see what leaves your machine. Your account code never does. If it finds nothing it says which of the three ordinary reasons might apply rather than reporting a failure — the storage-network copy was never switched on, the storage was paid for by a wallet the account code cannot derive, or the account holds only large files, which travel on their own.

Fixed the published recovery program still calling the recovery list a map in ninety-seven places.

The rename shipped to the website and stopped there. The program somebody runs on the day NMTS is gone went on using the old name in its help text, its error messages, its documentation and the format documents beside it — because the checker that guards the rename had been given a list of four files by hand, and went green. It now reads the whole of what gets published, so a file written tomorrow is covered the day it is written. The machine names are untouched: the file extension, the option you type, and the identifiers inside the format are all still what they were, because copies are already on people's disks and a parser looks for names rather than words.

Fixed a file's storage status running past its column on the English drive.

The status column is a fixed width, and the longest English sentence it can print — the one saying a file's storage term is not recorded — overran it by 13px at 1280 and 1440. It now wraps onto a second line instead: the column keeps its width, the text keeps its size, and only the rows with a long status get taller. Korean is unchanged, character for character. What let this stand: the width walk that guards this row only ever visited the Korean screens, and English is the default language here.