Version 0.83.0

On the comparison page, the pointer to the Privacy Policy is a working link instead of a 「준비 중」 label.

The panel that lists what NMTS can and cannot see says the full list is in the Privacy Policy — and next to that sentence sat a label saying the document was still being prepared. It has been published since 4 August. A label standing in for something that already exists sends people away from it exactly like a dead link does.

Leaving the community board, or turning off what you agreed to there, no longer depends on which build you are on.

NMTS is preparing a preview build that some accounts will be able to opt into, and because a preview can write things an older build cannot read back, requests that write are refused when the build sending them is not the one the account belongs to. That refusal was reaching things it should never have reached: leaving the board, turning either board consent switch off, marking a moderation notice as read, giving credit-paid storage back, and turning off the storage-network copy of your recovery list. Every one of those is you stopping something, and “your build is out of date” is not an answer you may be given when you are trying to stop something, so none of them waits for a build any more. Writes that create something in a format an older build cannot read still wait, and that is the point of the rule.

A refused change to your board settings no longer erases the address your moderation notices go to.

The board settings screen carries two consent switches and one contact address for moderation notices. If a single request changed both halves and the switch half was refused, the contact half had already been saved — so an empty address wiped the stored one, you were then told the request failed, and nothing on the screen said the address was gone. NMTS’s own screens never send both halves in one request, so this needed a hand-written client to reach; it is fixed regardless, because the next screen change would have reached it. The rule the endpoint now keeps is simple: every check runs before anything is written.

A day's writing allowance is no longer spent by a post that failed to save.

The board allows two posts and eight comments a day. The allowance was counted down first and the post written afterwards, in two separate steps — so if the second one failed, the allowance was gone with nothing to show for it and no way to get it back. The two now happen together or not at all.