aboutsummaryrefslogtreecommitdiffstats
path: root/dev.js
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-09-10 14:02:58 -0700
committerAdam Soltys <[email protected]>2026-09-10 14:02:58 -0700
commit1c34bb343c47f6e200575bac967959656ae7becb (patch)
treedb3a5aa553d36f087fa00bab78bd310f90c2f2c8 /dev.js
parent521cccbb60546190a91ae126164a456cc3b749bd (diff)
downloadcoinosv3-1c34bb343c47f6e200575bac967959656ae7becb.tar.gz
coinosv3-1c34bb343c47f6e200575bac967959656ae7becb.zip
Zaps in chat, and a bolt + sats tally on chat messages, DMs and posts.
Chat and DM message sheets grow a ⚡ Zap item (not on your own messages), riding the same one-tap flow as a post zap — Ark first, Lightning fallback, the amount remembered from the first time. A chat message is a rumor with an id like any event, so the zap e-tags that id; the public receipt reveals nothing but the id. Every post row, chat bubble and DM shows how much it's been zapped as a little amber bolt + sats chip (1.2k / 21k / 1.5M), fed by the public receipts that e-tag it: NIP-57 kind 9735 (amount from the bolt11, the zap request's amount as fallback) and coinos' own Ark receipt, kind 9737 (network-checked). Summed per id, deduped by receipt; underlined when one of ours is in it. Ids are asked once each (batched per paint, 150 per REQ), and ONE live subscription follows the ~200 ids most recently on screen so a zap landing while you watch — yours included, rechecked at 4/12/30s — shows up without a reload. The tally chip is itself a zap button on others' messages. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01URmfo8VimCNkw6Y7JndYrv
Diffstat (limited to 'dev.js')
0 files changed, 0 insertions, 0 deletions