Version 0.72.0

When a report about a file is made out, the three measures our terms name can now actually be carried out — and each one is written down.

Section 12.5 of the terms names what we can do when a report is made out: remove the share record, remove the file record, and stop serving the account involved — and until today there was no machinery for any of the three, so acting on a notice would have meant an operator typing a statement straight into the live database, with no record of what was done and no way back. There are now six operator endpoints and one script, and each measure leaves a row saying which measure, on what ground, and when. Three things are deliberately true of them: removing a file record requires the file and its owner's public code together, so a mistyped id matches nothing rather than somebody else's file; stopping an account takes effect on the next request rather than the next sign-in and never refuses an erasure, because the right to leave is not a service we can stop; and the ground recorded is one of five codes rather than free text, because an identifier only goes into that record if erasing an account can take it back out. The encrypted bytes on the storage network are untouched by all three, exactly as section 12.6 says, and there is still no form inside the product for reporting a file.