aboutsummaryrefslogtreecommitdiffstats
path: root/src/i18n.js
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-09-14 14:57:27 -0700
committerAdam Soltys <[email protected]>2026-09-14 14:57:27 -0700
commitfd3a35a2645b91e70f25f96282d9b8abf8b6562f (patch)
tree53eed290c5f0917acad26609fb27491451f50a84 /src/i18n.js
parent9a4bc457f3b18afdc7a493672bb1277fa4d956fb (diff)
downloadcoinosv3-fd3a35a2645b91e70f25f96282d9b8abf8b6562f.tar.gz
coinosv3-fd3a35a2645b91e70f25f96282d9b8abf8b6562f.zip
A zap on a chat message shows the message, not "Fetching note…" forever.
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 <[email protected]> Claude-Session: https://claude.ai/code/session_01QYJfZ4A1TDCEY4Foq3CApR
Diffstat (limited to 'src/i18n.js')
-rw-r--r--src/i18n.js1
1 files changed, 1 insertions, 0 deletions
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',