Version 0.94.0

You can make a key on the account screen for a program you run.

A key lets a program reach the server for your account without holding your account code, so it can list, download and upload but cannot open anything your code opens. You choose what it may do and how long it lives, up to ninety days, and the account screen takes it back at any time. A key alone works under tight limits until somebody passes the check below.

A person can raise a program's limits by typing a short code at nmts.me/verify.

The program prints a code and an address; whoever types it there lifts that account's keys to the ordinary limits for four weeks and opens the free-trial pages to them. The page needs no sign-in, because the person holding the code may not be signed in anywhere. The code works once, stops working after ten minutes, and is not your account code — nothing that page can do reveals whose account it raised.

The command-line tool takes a key, reads a file without leaving it on the disk, says what runs out soon, and clears the trash.

There was no way to hand it a key at all, so it now takes one the same three ways it takes an account code and never as a command-line argument. Reading one stored file used to mean writing plaintext to the disk; it can now hand the bytes straight to whatever is reading it, after the same checks. It also lists files whose bought storage runs out soon, and drops trash entries past their thirty days — that one asks every single time, because it cannot be undone.

A key can now share a file with another account, and take that share back.

Sharing was closed to keys because a share cannot be recalled once the other side has fetched it. That is still true; what changed is where the decision is taken. Creating a share now needs a person to have passed the check above within the last four weeks, and the command-line tool asks once on each machine before it will do it at all. Taking a share back needs neither — refusing somebody the undo would be the wrong way for that to fail.

The list of what waits for your acceptance was missing the board, and had been since 11 August.

When the documents change, that screen names every act that waits for your acceptance, and anything missing from it reads as something that still works. Writing on the board has waited since the board opened, and the screen said nothing about it — a check exempted routes that sit behind a switch, and could not tell whether the switch was on. Six acts joined the list, and the exemption now carries whether the switch is on where you use the product.