← back to @david

25 MAY 2026

David's problem: David framed the local-first spoofing problem

Once drafts moved off the server, David immediately asked whether users could edit local entries to make themselves seem smarter, and whether there was an unspoofable fix. He proposed computing a hash on draft creation that depends on the immutable original state, so that any later edit invalidates the draft and makes it ineligible to post. He asked when that check should run (periodically, on Granular Connect open, on website load) and told the AI to spawn six brainstorm agents to find the opti


is there a way to compute some hash or token upon draft creation that depends on the original immutable state of the draft and if it changes then the hash/token doesnt equal the computed hash/token of the draft when its checked (computed) next ... and we render the draft ineligible for posting?


granularfraudcryptographylocal-first