Version 0.95.0

A program you gave a key to can see how many credits are left.

It could quote the price of an upload and then spend, and had no way to say you were nearly out. The one address that reported the balance also carried the act that erases the account, so it could not be opened to a key; there is a separate address now that reads the balance, the ceilings and how much is stored, and can do nothing else. A key that may only spend, and not read, still cannot see it.

An account used only from a terminal can now be sent files.

Receiving a share needs the account's public code published, and only a browser could publish it. A program with a key can now do it. That value is not chosen — it comes from your account code — and publishing it cannot be undone, which is why the command asks for it separately rather than doing it on its own.

A program can build your recovery files, but only if it proves your account code in the same request.

The address that lists everything stored is the quickest way to copy out an account's index, so a key alone has never been enough for it and still is not. A program that also proves the account code may now read it and record where a recovery list was written. A key on its own hears a refusal naming what is missing, and a wrong proof counts only against that key — it can never lock you out of the browser the key is taken back from.

The recovery program can be downloaded and run, instead of being built from source.

It restores files from the storage network with your account code and a recovery list, and until now getting it meant installing a compiler — which is a poor thing to ask of somebody who has just lost access to their files. There is one file for each of Linux, macOS and Windows on its releases page, with a checksum list beside them. The checksum shows the bytes are the ones that release published; it shows nothing about who published it, and the source and the steps that built it are in the open for that.

Making a key on the account screen, and taking one back, were both refused. They had been since keys opened yesterday.

Both acts ask you to type your account code again, and the server was also demanding the short check a signed-out visitor passes — which the account screen has no reason to show you, because your session already carried it, so every attempt answered with a refusal that named the check. It is no longer asked a second time on a screen you are already signed in to, and the doors that exist before you sign in are unchanged. Nothing became reachable that was not reachable before.