aboutsummaryrefslogtreecommitdiffstats
path: root/src/features/messages.js
Commit message (Collapse)AuthorAgeFilesLines
...
* Threads: climb to the real root, and look for it on the right relays.Adam Soltys2026-09-211-8/+39
| | | | | | | | | | | | | A client that tags only the note it answered leaves the root unnamed, so the note it replied to was taken as the root and the thread opened with its first post missing (a reply at the top wearing a "reply" badge). The loader now climbs: when the note it resolved as the root is itself a reply, it fetches that note's root and re-roots the thread, a few hops at most. The root is also looked for on the participants' relays and the e tags' relay hints, not just the reply author's. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tmfg8k5f3TbNJS34qiqHAp
* Starter feeds: #gardenstr only until a Bitcoin follow pack is chosen.Adam Soltys2026-09-211-5/+4
| | | | | Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tmfg8k5f3TbNJS34qiqHAp
* New identities start with something to read: Adam and coinos followed, a ↵Adam Soltys2026-09-211-0/+62
| | | | | | | | | | | | | | | Bitcoin feed, and #gardenstr. A wallet the wizard made from fresh words, or a sign-in that found no wallet on its identity, gets one kind-3 update following the two coinos accounts (a sign-in identity only if it follows nobody yet), plus two starter feeds. The Bitcoin feed has a follow-pack slot (STARTER_BITCOIN_PACK) and reads the #bitcoin topic until a pack is chosen; #gardenstr shows what a topic feed is. Once per identity. The feed test now runs through the real first run, reading the words off the screen. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tmfg8k5f3TbNJS34qiqHAp
* Point of sale: /pos, a per-device till mode, an on-screen pad — and off ↵Adam Soltys2026-09-211-1/+1
| | | | | | | | | | | | | | | the Receive tab. v3.coinos.io/pos opens the point of sale once a wallet is up (claimed at boot before any feature reads the path), so the till can be bookmarked or put on a home screen. Settings → Payments gains "Start in point of sale on this device" (localStorage, not synced: the till, not every phone the owner carries). The amount and the custom tip get a 3×4 pad that edits the same field a keyboard or a paste would. The button under the payment address on Receive is gone. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01Tmfg8k5f3TbNJS34qiqHAp
* Profile: Messages opens the DM even when the profile sits over a thread.Adam Soltys2026-09-211-1/+5
| | | | Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Deep links: /note1… and /nevent1… open the thread; nostr:note intents ↵Adam Soltys2026-09-201-3/+17
| | | | | | | | | | route there; posts name the NIP-89 handler. A NIP-89 handler event (kind 31990, d=coinos) under the coinos key points njump and other pickers at /<npub> for people and /<note> for notes. The client tag on public posts now carries that coordinate. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Feeds: a following.space link is read before any naddr in the pasted text; ↵Adam Soltys2026-09-201-6/+4
| | | | | | the test clears its field between searches. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Feeds: packs are found by a few letters of their title, and by ↵Adam Soltys2026-09-201-13/+38
| | | | | | | | | | | | following.space's real link form. NIP-50 search only knew the packs the search relay carried — 'Niche Accounts' lives on damus and nos.lol, not relay.nostr.band. So the editor now indexes the wide relays' packs once per session and matches titles and descriptions by substring. A following.space link is /d/<id>?p=<pubkey>, not an naddr; both are accepted. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Feeds: follow packs from following.space (NIP-51 kind 39089) as a feed's people.Adam Soltys2026-09-201-7/+133
| | | | | | | | | | | A feed can name packs as well as people: the pack's current members are its authors, read from the pack event itself and cached on disk, refreshed hourly when a feed using it is opened — so a curator's change reaches the feed by itself. The editor takes a pasted following.space link or naddr, or searches packs by title (NIP-50 on relay.nostr.band). parseNostrRef learned naddr. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Messages: every saved feed is a row on the home list, under Following.Adam Soltys2026-09-201-1/+19
| | | | Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Feeds: Following is one of many; topics from search and #tags; the bolt is ↵Adam Soltys2026-09-201-53/+257
| | | | | | | | | | | | | | | | | | | | | | | | amber only for your own zap. Custom feeds live in the synced messages state — a name, everyone you follow and/or hand-picked people, and topics (hashtags, any of them; with people set as well, only their posts on those topics — the way a nostr filter composes authors and #t). Each feed keeps its own notes, clock and disk cache; a chips row under the feed title switches between them and + opens the editor (people are added through the same search the Send form uses). A word in the header search is a topic too: 'Posts on this topic' opens a session feed for it, as does a #tag in any post body — Save feed keeps it. Topic-only feeds read the big public relays as well as ours, since a hashtag has no author whose outbox we could follow. The zap icon used to go amber once anyone had zapped a post; now only when you have, like the heart. tools/feed-custom-test.js drives the editor, the relay filter, a tagged post landing, the #tag link, reload persistence and delete. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Chat: list sync stops rewriting a refused document every two seconds.Adam Soltys2026-09-201-2/+30
| | | | | | | | | | | | | | | | A relay refusing the community-list write (rate limit, ban) left the remote copy stale, and every resync asked for the same write again, each write echoing back on the live fragment subscription and triggering the next — five events every two seconds, forever. That filled relay.coinos.io's per-IP budget for the whole household, and the phone behind the same IP could no longer reach its remote signer: every NIP-46 request refused as rate-limited, every incoming DM stuck undecrypted (2026-09-20). An unchanged document is re-sent at most once per five minutes; a real change goes out at once. Our own echoes are ignored, and another device's write triggers a resync no more than once every ten seconds. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Notifications: a reaction, boost or zap opens its note with the who-panel ↵Adam Soltys2026-09-201-3/+8
| | | | | | unfolded. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Messages: the Notifications row's unread dot sits like a group row's.Adam Soltys2026-09-191-4/+4
| | | | Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Zaps: the sound can be switched off — from the held bolt or Settings → ↵Adam Soltys2026-09-191-4/+9
| | | | | | | | | | Nostr. A prefs flag (zapSound, absent = on) synced with the zap amount. The strike and the tally are unchanged; only the clip stays quiet, and the clip chunk is not even fetched while it's off. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Zaps: tap again while one flies, hold the bolt to change the amount.Adam Soltys2026-09-191-45/+125
| | | | | | | | | | | | | | | | A pending zap no longer refuses the next tap: the optimistic tally keeps one entry per zap and matches each report and receipt to the oldest it can describe, so two default-amount zaps stack, settle and hand over to their receipts one at a time. Instant post zaps run off the send screen's zap slot, so a second tap can't evict the one still resolving, and send action ids are unique within a millisecond. Holding ⚡ (500ms) opens the amount screen in an edit mode — Save alone, or Save and zap this note — from the action bar and the chat chips alike; the press's timer lives on the element so a background repaint mid-press can't turn a lifted finger into a hold. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Feed: live posts go straight in; the pill is a notice, not a gate.Adam Soltys2026-09-191-32/+30
| | | | | | | | | | | | | "Nothing new ever arrives" was four posts waiting behind the pill on the phone and two on the laptop. Now a post that arrives on its own goes into the feed at once, wherever you are: at the top it opens itself under your eyes; further down it goes in above the fold with the page held still (holdScroll), and the pill only says how many are up there. Its tap scrolls to the top; reaching the top by yourself clears it, since only the pill repaints and the keyed rows stay put. The small catch-up case gets the same notice. The feed-live test says so. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Feed: coming back settles once — a few new posts above you, a lot means ↵Adam Soltys2026-09-191-4/+73
| | | | | | | | | | | | | | | | | | | | | | | | the top. The catch-up on arriving at the feed asked every relay for its newest posts with no lower bound, and everything not already in the fifty-post cache went behind the pill, chunk by chunk: the count climbed in steps and stopped at the pending list's cap of 200, whether there were 12 new posts or 500. Now the pass is buffered and settled once, after every relay has answered. Posts older than the newest we had are gap fills and merge silently. Up to twenty genuinely new posts go in above what you're looking at with the page held still (holdScroll: the row at the top of the viewport stays put, measured after the paint so a browser that anchored on its own isn't corrected twice), so scrolling up reveals them in order, newest at the top. More than twenty means you've been away: the feed goes to the top, at the newest post, as on a fresh open. The window grows only by posts landing inside it, so a catch-up doesn't paint two hundred rows. The pill is now only for posts that arrive live while you read further down. The feed-live test covers the three arrivals, and its stale checks (auto-flush on scrolling up was removed on purpose; a fresh <img> reports complete a task late) now say what the app does. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Zaps: the sound, the sender, and one action bar for every post.Adam Soltys2026-09-181-96/+138
| | | | | | | | | | | | | | | | | | Tap feedback: a bolt strike, the amount popping off the button, the post trembling, and the zap.mp3 clip. The clip is 62KB of base64 and messages.js is boot code, so it is its own chunk, fetched once a zappable post is on screen and played inside the tap once loaded; the standalone build inlines it. Ark zap receipts are signed by the wallet key, which has no profile: they now carry the login identity as the sender (NIP-57's P tag), readers prefer it, and our own older receipts read as us. The action bar is the same six slots on every post: the zap button and the who-reacted chevron are always there (inert until they have something to do), so the first zap no longer reflows the row, and you can zap your own posts and messages. Community rows centre their unread dot off the edge. Also in here: reactions with custom emoji, reply-composer focus under the tapped post, profile fetch retry, and Lightning zap failures that say so. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Feed: the zap tally rides on the action-bar bolt, not the header.Adam Soltys2026-09-171-6/+21
| | | | | | | | | The sats total used to sit up by the timestamp as its own chip; now it is the count on the zap button, like likes and boosts have theirs. Amber once anyone has zapped, breathing while ours is in flight, and shown read-only (no zap handler) on posts you can't zap so the number still reads. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* A thread reply is a growing textarea: Enter sends, Shift+Enter breaks the line.Adam Soltys2026-09-171-5/+21
| | | | | Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01JuwQqNWtDJcxPWtEm9134z
* Pay from a profile opens the Send form, not a lingering payment detail.Adam Soltys2026-09-161-2/+2
| | | | | | | | | | | A tapped history row claims the whole tab area whichever tab is picked, so jumping to ui.tab = 'send' from a profile's Pay button (or a zap's form fallback) with a renewal's detail still open showed that detail instead of the form. showSend() closes any open detail first; the three feature paths that jump to Send use it. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01JuwQqNWtDJcxPWtEm9134z
* A note that wasn't found is asked for again, with the reactor's relay hint.Adam Soltys2026-09-161-13/+22
| | | | | | | | | | | | A reaction's target was fetched once from our relays, and a miss was final for the session — so with our own relay down for an evening, a reply that sat on four relays showed as "no longer on your relays" until a reload. A missing note is now retried when next wanted (half a minute on), the reaction's e-tag relay hint rides along, and tapping the row asks again instead of doing nothing. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01JuwQqNWtDJcxPWtEm9134z
* Feed: what arrives waits behind the pill; the count bumps; no auto-flush.Adam Soltys2026-09-161-13/+26
| | | | | | | | | | | | | | Posts a refresh found slid in a beat after the cached page painted, moving what you had begun reading, and reaching the top of the page let waiting posts in with a re-render under a finger on its way to the pill — the tap landed on the post beneath. Now everything that arrives after the first paint, the boot catch-up included, waits behind the pill wherever you are; the pill is a keyed node whose count bumps on each change; and a tap scrolls to the top before painting so the new posts open under your eyes. A rebuilt follow list still rebuilds the feed in place. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01JuwQqNWtDJcxPWtEm9134z
* A bare @npub in a message resolves to the person's name.Adam Soltys2026-09-151-4/+8
| | | | | | | | | | Vector writes a mention as @npub1… with no nostr: prefix; ours only resolved the prefixed form, so the raw key sat in the bubble. Bare npubs and nprofiles, with or without the @, now render as @name and open the profile, like the prefixed ones. Keys inside URLs are left alone. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01JuwQqNWtDJcxPWtEm9134z
* A changed reaction stays changed: the fold keeps the newest, not the last to ↵Adam Soltys2026-09-151-3/+20
| | | | | | | | | | | | | arrive. One reaction per author was folded as "last one in wins". A reload's backfill hands reactions back in relay order, so a flame swapped for confetti came back as the flame. Rooms, DMs and the public page now keep the newest by the rumor's own clock, and an optimistic send stamps its time so an older one arriving afterwards stays out. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01JuwQqNWtDJcxPWtEm9134z
* Community reactions carry the target author's p tag, as Concord specifies.Adam Soltys2026-09-151-1/+4
| | | | | | | | | A reaction sent from v3 never showed in Vector: its parser requires the NIP-25 p tag naming the reacted-to message's author (CORD examples §2.3 has e, p and k), and ours sent only e and k. Added. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01JuwQqNWtDJcxPWtEm9134z
* Cached faces warm from the wallet's own namespace, once its keys are in.Adam Soltys2026-09-151-0/+11
| | | | | | | | | | | | | On the phone the profile cache was intact — 150 faces, our own with a thumbnail — yet an offline boot drew a punk in the header. The header asks for a face before a silent sign-in has finished resuming, and the warm-up ran then: it read an empty slot under a keyless namespace and counted itself done. Online the relays refilled the map and nobody saw it; offline nothing did. The warm-up now waits for the wallet's keys and runs again at feature init, from the right namespace. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01JuwQqNWtDJcxPWtEm9134z
* Offline, the chat shows what it read: messages cache on arrival.Adam Soltys2026-09-151-2/+16
| | | | | | | | | | | | | | | | The room cache was written only on our own sends, deletes and attachments, so a member who only reads had nothing on an offline boot — "No messages yet" over a room read the day before, and no faces or names with it. Messages now persist as they arrive (debounced past the backfill burst), so the last fifty per channel are there without a network. Our own face never waits its turn for a thumbnail and never gives it up to the budget, so the header avatar paints offline too. tools/offline-cache-test.js boots the PWA build, caches a room, reloads fully offline and checks messages, names and thumbnails are all there. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01JuwQqNWtDJcxPWtEm9134z
* Chat keeps its relay subscriptions alive while the app is on screen.Adam Soltys2026-09-151-16/+75
| | | | | | | | | | | | | | | | | | | | | New messages rang in Vector but sat unseen in v3 until a reload. The resume hook only rebuilds subscriptions after an absence it was told about; a socket that errors while the page stays visible (a wifi hop, a laptop lid, a phone freezing the tab without the away timer noticing, another tab clearing that timer first) is dropped from the nostr-tools pool with every subscription it carried, and nothing dials it again. A watchdog now runs whenever the app is on screen: on focus, on becoming visible, and every ten seconds between. It asks the pool whether each relay the inbox and the rooms listen on still holds a live socket (a dial hung past 20s counts as dead, and a relay that closed a subscription on us counts too) and rebuilds the lot when one is missing, dropping a stuck relay first so the rebuild dials afresh. Rebuilds retry on a growing backoff while a relay keeps refusing. tools/chat-watchdog-test.js errors every socket under an open room and checks the recovery. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01JuwQqNWtDJcxPWtEm9134z
* A pack link in chat adds the pack in place; coinos has its own share link.Adam Soltys2026-09-151-14/+39
| | | | | | | | | | | | | | | | | | Tapping "Emoji pack" on a phone opened Vector: the chip was an outbound link to vectorapp.io, a domain the Vector app owns. The chip is now a button — one tap adds the pack right here, nothing leaves coinos. Packs also get a coinos share link, v3.coinos.io/emojis/pack/<naddr> (copy it from the picker's pack row). The Android app already claims every v3.coinos.io path, so on a phone that link opens coinos, which adds the pack once the wallet is open. Pack links from any host render as the chip; the naddr's kind is what's checked. Pack changes now save at once (learned shortcodes stay coalesced) — a remove followed straight away by a navigation was lost to the debounce. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01JuwQqNWtDJcxPWtEm9134z
* A reply's quoted line shows its custom emoji as pictures.Adam Soltys2026-09-151-6/+30
| | | | | | | | | | The quote above a reply bubble, the composer's reply bar, and the same on the public /chat page rendered the raw :shortcode:. They now run the one-line snippet through the same NIP-30 tokenizer, cutting on text so a shortcode is never sliced in half. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01JuwQqNWtDJcxPWtEm9134z
* Custom emoji in chat: :shortcodes: render as pictures, packs sync with Vector.Adam Soltys2026-09-151-26/+353
| | | | | | | | | | | | | | | | | | | | | | | A message from Vector says :pika_wave: and carries a NIP-30 ["emoji", code, url] tag for it; coinos showed the bare shortcode. Now the bubble shows the picture (in rooms, DMs, the feed and the public /chat page), a bubble that is only one to three of them shows them big, and a :code: reaction chip is a picture too. Sending: every :code: you type that resolves travels with its tag, so the other side renders it whether or not they hold the pack. Shortcodes come from packs you hold (NIP-51 kind 30030 sets) and from what you've seen in chat, so anyone can answer a :pika_wave: with one. The composer autocompletes on ":pi" (Tab/Enter takes the first), the reaction picker lists custom emoji first, and Vector's pack share link renders with an Add button; a pasted naddr works too. Packs live on your kind 10030 list — the one Vector reads and writes — so a pack added in either app appears in both. tools/emoji-test.js drives the real coinos room headlessly and checks all of the above. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01JuwQqNWtDJcxPWtEm9134z
* Opening a reply scrolls the thread to that reply.Adam Soltys2026-09-151-1/+18
| | | | | | | | | | A thread opened from a reply highlighted the reply but never scrolled to it, so in a long thread it sat below the fold and the page looked like it had missed. The thread now scrolls the focused note into view after its paint — and if the replies are still loading, after the render that brings them. Opening the root itself means the top. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* An @handle in a bio or post opens the people search for that name.Adam Soltys2026-09-151-1/+21
| | | | | | | | A bare @name carries no key, so nothing can resolve it for certain — but it can be a tap that opens the search with the name filled in. The @ inside an email or nip05 is left alone, as is anything inside a URL. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Join suggests communities from the Vector Hub, searchable, beside the paste box.Adam Soltys2026-09-141-7/+60
| | | | | | | | | | | The Join panel used to be one empty box asking for a link nobody had. It now lists the Vector Hub's public communities under it — icon, name, member count, category, description, sorted by size, marked when you're already in one — fetched on demand and kept for the session. The same box takes a link or filters the list; a tapped suggestion previews exactly like a pasted invite, since every listing is a CORD-05 link. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Invite links open in Vector, communities sync across Concord clients, and ↵Adam Soltys2026-09-141-35/+213
| | | | | | | | | | | | | | | | | | | | | | | | | | | any emoji can be a reaction. Vector's bundle parser has no default for a channel's key and epoch, so a coinos invite — which sent only id and name — failed its whole JSON parse and the link did nothing there. Every channel entry now carries key and epoch (a public channel's key is the community_root at the base epoch, CORD-05 §1), and bundles minted before this are re-signed at the same coordinate once per device, so links already shared start working. Concord clients now keep their Community List as kind 33302 fragments (CORD-02 §8): addressable per index, NIP-44 to self, 32-byte values as unpadded base64url, embedded join material without its community_id, seed omitted when it equals current. coinos read and wrote only the retired single-event 13302 on its own two relays, so a community joined in Vector under the same key never appeared here. The fragmented list is now read from our relays, the stock CORD set and every held community's relays, merged, and written back in the same shape; the home view re-syncs after a minute and a live subscription brings a fresh write straight in. 13302 stays for older coinos devices. The reaction row keeps its quick emojis, recents first, and a + opens a searchable picker of a few hundred more — eyes included. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* A picture can be sent to a channel or a DM, encrypted, and read by Vector.Adam Soltys2026-09-141-7/+154
| | | | | | | | | | | | | | | The composer grows a paper clip. A picked file is encrypted under a fresh AES-GCM key and 16-byte nonce, the ciphertext uploaded to a public Blossom host that takes anonymous blobs (blossom.ditto.pub, then nostr.download as a fallback copy), and the pointer posted the way Vector posts it: a kind-9 with empty content and a NIP-92 imeta tag carrying url, mime, key, nonce, both hashes, size and dimensions. In a DM it is a NIP-17 kind-15 file message with the same fields as flat tags and the url as content, wrapped to the peer and to ourselves. Kind-15 file messages are now accepted on receive too, rendered like any attachment, and previewed as a photo in the thread list. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* A picture sent to a channel shows up as a picture, not an empty bubble.Adam Soltys2026-09-141-1/+86
| | | | | | | | | | | | | Vector attaches files as NIP-92 imeta tags: the blob is encrypted with a one-off AES-GCM key before it reaches Blossom, and the tag carries the url, mime, key, nonce, plaintext sha256 and dimensions. Such a message has no text, so the bubble rendered blank. The blob is now fetched (fallback hosts too), decrypted in the browser, checked against the hash, and shown from an object URL — a grey box its shape while it loads, tap to view full size, other file types as a download by name. The same tags render in DMs. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Logging out leaves one identity, not everyone on the device.Adam Soltys2026-09-141-7/+18
| | | | | | | | | | | | With several identities signed in, the profile's Log out now signs out only the current one: its accounts leave the session, directory, cache and vault, the others stay put, and the next identity takes the screen. The confirmation names who is leaving and says whether they can sign straight back in (a nostr login) or need their recovery phrase (a bare seed). Logging out of every account is a second, explicit button. Alone on the device, Log out is unchanged. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* A community whose invite grants no channels still shows its public ones.Adam Soltys2026-09-141-0/+12
| | | | | | | | | | A Vector invite carries only private channel keys, so its channel list can be empty; the public channels arrive through the Control fold. The room only ever subscribed to the invite's channels, so FOSS Apps folded to 58 members and "No messages yet". Channels the fold discovers are subscribed as they land, and warm from the message cache on reopen. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* A community that has been refounded reads and writes at its current epoch.Adam Soltys2026-09-141-26/+74
| | | | | | | | | | | | | | | | | | | | | | | | Vector communities (Nostr Talk, FOSS Apps) sit at root epoch 1 after a refounding. coinos derived every channel stream at epoch 0, so it read and posted to an address nobody else used: five messages from coinos users where Vector showed months of history. Public channels now follow the base epoch (CORD-03), private ones their own key and epoch from the join material; the epoch tag on every rumor matches the stream that carried it. The Control Plane is read at the invite's control_pk (CORD-02 §5 split) and decrypted under the root-derived key, so metadata, icon and channel definitions fold for a post-split community; the legacy derivation is kept for the built-in coinos community, which still writes through it. Guestbook snapshots (3312) from the owner seed members after a refounding, so the count matches Vector's. Join material carries control_pk and private channel keys through the Community List and direct invites, and the list merge heals an entry that predates them. A pasted invite previews under the Communities heading where the paste box was, instead of at the top of a page the user had scrolled past. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Messages sent while the app was away arrive when it comes back.Adam Soltys2026-09-141-16/+53
| | | | | | | | | | | | | | | | | Two ways a DM or a room message went missing. A phone freezing the tab errors the relay sockets, and an errored socket is one the pool gives up on — so every wrap subscription died silently and nothing sent after the freeze ever arrived, until a reload. Coming back from the background (or back online) now rebuilds the DM and room subscriptions; their windows overlap what is held and seen wraps are dropped before any decryption. And a remote signer that never answered was read as "this wrap isn't ours": three such silences and the wrap was remembered as seen and lost on that device for good. Silence now means "try later" — uncounted — and the drain stops at the first one rather than burning tries on the rest. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01QYJfZ4A1TDCEY4Foq3CApR
* A new identity starts with an empty Notifications list.Adam Soltys2026-09-141-0/+4
| | | | | | | | | | Logging out and opening another account kept showing the last account's replies and zaps: the list lived in memory across the switch, alongside the feed and tallies that were already being cleared. It is cleared with them now, together with the who-zapped map and any open panels. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01QYJfZ4A1TDCEY4Foq3CApR
* A reply or a mention on nostr can buzz your phone.Adam Soltys2026-09-141-1/+23
| | | | | | | | | | | | | The push notifier now watches kind 1 for the user's pubkey beside DMs and zap receipts, and pushes who, what, and an excerpt. The worker shows "New reply to your post" or "You were mentioned" with the text, and a tap lands in the Notifications list — as ?open=notifs when a window has to be opened, or as a worker message when one already is. It has its own switch, "Replies and mentions on nostr", in Settings → Notifications, on by default like payments and DMs. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01QYJfZ4A1TDCEY4Foq3CApR
* A zap on a chat message shows the message, not "Fetching note…" forever.Adam Soltys2026-09-141-8/+41
| | | | | | | | | | | | 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
* A notification's excerpt names the people it mentions.Adam Soltys2026-09-141-2/+9
| | | | | Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01QYJfZ4A1TDCEY4Foq3CApR
* The zap amounts in the new panels use the feature's own formatter.Adam Soltys2026-09-141-2/+2
| | | | | Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01QYJfZ4A1TDCEY4Foq3CApR
* Who reacted, and what happened to your posts.Adam Soltys2026-09-141-5/+247
| | | | | | | | | | | | | | | | | A chevron on a post's action bar, shown once anyone has reacted, boosted or zapped it, opens a panel that says who and with what: each zap on its own line with the amount and any message, then each emoji with the faces and names behind it, then the boosts. Every face opens the profile. The zap tally now keeps who sent each receipt, not just the sum. And a Notifications list on the chat home, under the feed: every like, boost, zap, reply and mention that names you, one filter on the relays we read, painted from last time while the relays are asked and live while open. A row opens the post it is about — or the reply itself — and the entry counts what arrived since you last looked. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01QYJfZ4A1TDCEY4Foq3CApR
* A video keeps playing while the page repaints.Adam Soltys2026-09-141-0/+7
| | | | | | | | | | | | The page repaints in the background all the time — a zap count, a profile landing, the thirty-second sync — and every repaint rebuilt a post's YouTube box as poster-plus-play-button and patched the live box into that shape, which threw the playing iframe out a few seconds into every video. Once playing, the box is the viewer's: it is frozen against the morph and left exactly as it stands. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01QYJfZ4A1TDCEY4Foq3CApR
generated by cgit v1.2.3 (git 2.51.0) at 2026-10-15 20:27:23 +0000