Version 0.87.2

What an inquiry may carry alongside it now has a fixed shape, not just fixed section names.

The inbox is the one place plaintext leaves your device on purpose, so what rides with a question is meant to be narrow: five named sections, each a short list of facts you ticked and saw before sending. The server checked those five names and nothing else, so one section could be thirty kilobytes of text and it would land in the one column a person on our side reads. Each section is now a flat set of name-and-value facts (text up to 1,000 characters, 32 fields, names up to 64 characters), and the files section is a list of file entries. Nothing a browser actually sends changes; what is gone is the room for anything else.

A value from the chain service can no longer write a line of its own into the server's log.

When a number came back in a form the server could not read, it wrote that value into its log exactly as received. Those numbers come back from a public node NMTS does not run, and a value carrying a line break writes a second, invented line — into the record an incident review reads. The same rule was already in place in the other direction and said so in its own comment. Values are now put on one line and cut at 120 characters, and what arrived is still readable, because a log that discards it tells whoever reviews an incident nothing.

Three different values had gotten the same names in our operator tools, and one of those names was a secret.

There is the account code (32 characters, yours alone, never sent to us), the account identifier (how our server looks a row up), and the public code (the one you use to exchange files). The tools we use to act on a report asked for «the account code» when they meant the identifier, and the server’s own note called the identifier «the public code», which it is not. Nothing acted on the wrong account, because both values are the same length so a wrong one parses and then matches nothing — what the wrong names could have produced is someone on our side asking a person for their account code. All three are now named apart, in the server and in both tools, with the difference written down where each is used.