v2.6.2 The confirmation dialog says what it is about to do, and condenser's own bookkeeping stops travelling to the signer (MRs !204, !205, !206). - The dialog named the chain's operation rather than the action the reader had asked for. Muting a post, flagging it, pinning it, following an account, subscribing to a community, changing a role, setting a user title and editing community settings are all `custom_json`, so every one of them asked for confirmation of "Custom Json"; claiming rewards and deleting a post named their raw operation too, and a post published from the assistant was called a comment. The action is carried inside the operation's payload, so the dialog reads it from there and names it. An explicit title still takes precedence, so the ones already set by the editor, the voting control and the reblog control are unchanged, and an operation with nothing mapped still shows its raw type rather than being given an invented label. Eighteen titles across the nine locales. - Undoing a follow and undoing a mute are the same operation on the chain: a `follow` whose `what` is empty. Nothing in the payload tells them apart, so unmuting an account asked the reader to confirm unfollowing. The two callers now name the action themselves, since they are the only place that still knows which one was clicked. - `__config` carries condenser's own bookkeeping -- the title the dialog shows, the body an edit patches against, the message to raise on success -- and it was reaching the signer on every operation except a comment. A signing extension serializes the fields it is handed while the node re-serializes only the ones it knows, so the two disagree and the signature fails to validate; the comment path already rebuilt its operation without it for exactly that reason, and a reblog has carried one on a `custom_json` for some time. The broadcast now gets a copy without the field, and the originals are left alone for the hooks that read it afterwards. The plain-key path was never affected, which is why it went unnoticed. Note that v2.6.1 was tagged but never deployed, so a release from here carries the reply invitation of that tag as well.