Withheld both directions; UTD persistence, redecryptor, metrics #29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
§10.4.3/§10.4.4: send m.room_key.withheld when refusing to share; received withheld codes mark UTDs non-retriable. Every decryption failure persists as a sealed UTD state with versioned cause taxonomy + isRetriable (CR-8); redecryptor heals in place on key arrival keeping item identity (CR-12); occurrence/resolution/time-to-decrypt via §7.
Deferred from #27 into this issue (adjacent to withheld/no_olm): olm unwedging — on an undecryptable olm message, claim a fresh OTK, establish a new session and send m.dummy (rate-limited per sender/device), alongside the one-time m.no_olm withheld the corpus expects. #27's machine returns sealed decryption outcomes but does not auto-unwedge.