From fd3a35a2645b91e70f25f96282d9b8abf8b6562f Mon Sep 17 00:00:00 2001 From: Adam Soltys Date: Mon, 14 Sep 2026 14:57:27 -0700 Subject: A zap on a chat message shows the message, not "Fetching note…" forever. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A receipt for a zap on a chat message or a DM e-tags the rumor's id, which no relay has ever held as an event — so the row fetched it by id and waited forever. The rooms and threads we hold are searched first: the row shows the message's text and a tap opens that room or thread. A post the relays really don't have says so instead of spinning. And a coinos zap's own receipt beside the LNURL server's is one row, not two. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01QYJfZ4A1TDCEY4Foq3CApR --- src/i18n.js | 1 + 1 file changed, 1 insertion(+) (limited to 'src/i18n.js') diff --git a/src/i18n.js b/src/i18n.js index 07a545c..290b514 100644 --- a/src/i18n.js +++ b/src/i18n.js @@ -211,6 +211,7 @@ const STR = { alertBoost: 'boosted your post', alertReply: 'replied to you', alertMention: 'mentioned you', + alertNoteGone: 'The post is no longer on your relays', postWho: 'Who reacted', feedFollow: 'Follow', feedFollowing: 'Following', -- cgit v1.2.3