Skip to content
zit Check-in [e0535646dc]
Login

Check-in [e0535646dc]

Overview
Comment:Abort the exchange on a message card whose visible arity is not the exactly two whitespace-separated tokens sync §11.2 mandates, since a bare or three-to-six-token form is a defined-operator arity failure under §5.2 rather than a silently continued card.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: e0535646dc6dc236eb92d5a04d9ad8b4a5679258ce80552e5ab076a2677783f5
User & Date: dmestas on 2026-07-13 19:18:08.021
Other Links: manifest | tags
Context
2026-07-13
19:45
Accept a non-canonically fossilized unversioned NAME instead of aborting the exchange, since sync §7.3 licenses no such receiver rejection and artifact §4.3 defines the defossilize decoder as error-free, and parse a cookie login value strictly by the §B.4 url-login-value grammar so fields split only on the literal + separator, escapes are lenient solely under HEXDIG-CI, and a %20 standing in for a separator is rejected. check-in: 3fd2c0ca4c user: dmestas tags: trunk
19:18
Abort the exchange on a message card whose visible arity is not the exactly two whitespace-separated tokens sync §11.2 mandates, since a bare or three-to-six-token form is a defined-operator arity failure under §5.2 rather than a silently continued card. check-in: e0535646dc user: dmestas tags: trunk
19:03
Gate the private igot no-phantom disposition on the receiver lacking private-content authorization so a granted client interns the hash and creates a phantom to pull the content, per sync §7.5 L2476-2483. check-in: 28a19941cd user: dmestas tags: trunk
Changes