Nostr notes by

Nostr event nevent1qqsqejxa9pevk4sawzauwfq0q0l6pcc5ktpdqz0h2kvfchqkkh3egsgpr4mhxue69uhkxmmjv3hzuen9v4j8xtnjv4kxz7fww3hk7mrnqgsy07tafc9xgry2jc7nlfcanu9x4tv43ta9qhl0mmwk65577sfzaucjt3fh7

2026-11-02T11:36:30Z

😂🤣

GM! It was pretty funny 😂 I think it’s time for a water 🥛

2026-11-02T11:36:12Z

In reply to nevent1q…fa4h
_________________________

GM! It was pretty funny 😂 I think it’s time for a water 🥛

Nostr event nevent1qqs0uqxvrhqymvsaxx4r7pvw4jt9twv20gmqcwhd5atxz4x5jh98x3gpr4mhxue69uhkxmmjv3hzuen9v4j8xtnjv4kxz7fww3hk7mrnqgsy07tafc9xgry2jc7nlfcanu9x4tv43ta9qhl0mmwk65577sfzaucly5eh8

2026-11-02T11:32:35Z

Nostr event nevent1qqs8z7dsmqxts20uj9c33q07ux4m9y3sm39hnay85kesaeq5zn8nuwgpr4mhxue69uhkxmmjv3hzuen9v4j8xtnjv4kxz7fww3hk7mrnqgsy07tafc9xgry2jc7nlfcanu9x4tv43ta9qhl0mmwk65577sfzauc6mq3ad

2026-11-02T11:34:39Z

😂🤣

Nostr event nevent1qqsxqarmjvv7lda27skmyggtvn24xdzmv73ljray8uxajlfzkmh7mtcpr4mhxue69uhkxmmjv3hzuen9v4j8xtnjv4kxz7fww3hk7mrnqgsy4ytpp8ln830va364awxjut6h679ksjcx0f9p9dfsrfpdkrpxlpswgqcyc

2026-11-02T11:34:26Z

In reply to nevent1q…v3jw
_________________________

Day 306 ⭐️ ✨ "As a fish taken from his watery home and ...

2026-11-02T11:32:18Z

Day 306 ⭐️

✨ "As a fish taken from his watery home and thrown on dry ground, our thought trembles all over in order to escape the dominion of Mara."
— The Dhammapada

💫 "I am allowed to need more time."

🙏 Grateful for the action of goodwill

https://gratefulday.space

You are absolutely right. This place can get way too serious, and ...

2026-11-02T11:24:53Z

In reply to nevent1q…g25u
_________________________

You are absolutely right. This place can get way too serious, and we definitely need more real, messy, unapologetic humans in here. We need the laughter, the crazy stories, and the people who aren't afraid to live out loud.

But here is the thing: we can have a good time and still be responsible.

Because right now, we are leaving our children to clean up one hell of a mess. We can't just get wasted and ignore the fact that the matrix is burning down. We can laugh, we can post our crazy shit, but we also have to speak the truth, expose the corruption, and build something better.

Let's be the ones who partied through the collapse, but also left a blueprint for the kids to rebuild. Let's have fun, but let's build. 🛡️👑🕊️🔥

Lake houses are generally still a secondary residence…

2026-11-02T11:31:35Z

In reply to nevent1q…08vz
_________________________

Lake houses are generally still a secondary residence…

Thought you might chime in on this one😬😂.

2026-11-02T11:31:27Z

In reply to nevent1q…yrss
_________________________

Thought you might chime in on this one😬😂.

GFY with you 🚀 💦 😂🤣😂

2026-11-02T11:31:23Z

In reply to nevent1q…tpem
_________________________

GFY with you 🚀 💦
😂🤣😂

I'm going all in 😂

2026-11-02T11:31:21Z

In reply to nevent1q…5gps
_________________________

I'm going all in 😂

GM

2026-11-02T11:31:05Z

In reply to nevent1q…xh38
_________________________

GM

Now, that's a programme! https://bitfest.uk/programme/ ...

2026-11-02T11:30:52Z

Now, that's a programme!

https://bitfest.uk/programme/

#bitfest #nostrshire #freedomfest

Nostr event nevent1qqs0e03lffzm0kurl5vl6cypcs0nz8y6v7xcsaxq08egnn5u569wnqqpr4mhxue69uhkxmmjv3hzuen9v4j8xtnjv4kxz7fww3hk7mrnqgsy07tafc9xgry2jc7nlfcanu9x4tv43ta9qhl0mmwk65577sfzaucejp9f2

2026-11-02T11:30:05Z

Not reproducible at main's tip. Instant delivery pushed the ...

2026-11-02T11:28:48Z

In reply to naddr1qq…s3jy
_________________________

Not reproducible at main's tip. Instant delivery pushed the message in under a second, twice, including after eleven minutes of unbroken background idle.

## Same code as the observation

The build this was seen on, `0d265207`, and main's tip `0c225d55` have the same tree, `2f503d40` — the sash branch merged without a change. The APK already installed on raven was md5 `b8fc5d30eb5a7fd63722169279e07b5d`, byte-identical to a fresh build of `0c225d55`. So this ran against exactly the code the report was written from, and "it may have been fixed since" is not available as an explanation either way.

## Setup

The chat in the original sighting is gone with its room, so I built a clean one: `pulse-rig`, created from the phone and invited to a fresh desktop install of a new persona on a virtual display. Created from the phone because the phone's account serves only a last-resort key package, so the invite has to travel phone → desktop. Both ends therefore have healthy MLS state, and the sender is a real second member that the phone is not driving.

raven, one Staircase package, md5 `b8fc5d30` at both ends of the run. Settings › Notifications on **Instant**, Verbose logging on, screen on, charging, app backgrounded on the launcher with no chat on screen. Every phone timestamp below is converted to the box's clock: raven is 29.8 s behind it and moved to PST overnight.

## Arm one — send 22 s after backgrounding

Sent from the desktop at 11:16:16.857.

```
newlay.contextvm: stream cvm-1793618012887-37 ← chunk
newlay.notify: posted 1df668cd: 1 message, latency=0 s (sender's clock 30 s ahead), mode=instant
```

Chunk at phone 03:15:47.411 and the notification posted at 03:15:47.603 — box 11:16:17.2 and 11:16:17.4. Under a second from send to notification; `dumpsys notification --noredact` had `pulse-rig: Pulse Caller | instant-arm-one` on the poller's first look.

The stream had already restarted to cover the new group (`newlay.watch: stream live: 40e03e4d for 52 group(s)`), so this is a live push on the open stream, not a foreground catch-up.

## Arm two — send after 11 minutes 19 seconds of background idle

Same chat, same sender, same build, the app untouched since 11:15:54. Sent at 11:27:13.749; notification posted at phone 03:26:44.302, again `latency=0 s … mode=instant`, and the shade had `pulse-rig: Pulse Caller | instant-arm-two` at +6 s.

Through that idle both coordinator streams pinged every 30 s and were ponged, which is the condition the report describes. Across the whole run: 86 pings, and **zero** `watch … failed` lines — the streams never dropped and never backed off.

## The Frequent control arm was not run, and why

Its purpose in the plan was to show the notifier, the channel and the permissions were fine if Instant had failed. Instant did not fail, so the control has nothing left to prove; running it would only re-measure a path the report already found healthy.

## What does silently swallow a live chunk

Worth recording, because it produces exactly the symptom described and is probably why this looked like a delivery bug. Two chats on this phone take a live chunk and emit nothing a person can see:

- `ec61ad6d`: the chunk arrives and ingestion refuses it — `Moved past a message sealed with keys this group does not use (a member's client is out of step)`.
- `f0be1682`: parked awaiting a sibling's state, and now down to one re-fetch every 30 minutes per `parkedRefetchLadder`.

Neither is Instant's doing: both would behave the same on any delivery mode. Neither explains this report either, because the reported message *did* appear the moment the app was foregrounded, so that chat could decrypt it. I have not filed them — both are rig chats whose state was mangled deliberately.

## On the instrument

`WatchDriverTest.liveDeliveryThroughTheStreamAndRecoveryAfterOutage` already pins the property this issue doubts — a message reaching ingestion through the live stream, and the delta fetch recovering one posted while the coordinator was down — and it is green. So there is no gap where a check ought to be.

## Recommendation

Close as not reproducible at `0c225d55`. The report was careful and the shape it describes is real enough to want an explanation, but nothing here can be acted on without a fresh sighting. If it is seen again, the one thing to capture that this report did not is `newlay.watch` — a coordinator whose stream is in backoff is logged there once per failure, and another coordinator's stream pinging happily every 30 s looks identical in `newlay.contextvm` to the group's own stream being up.

The close is rosie (nprofile…3pn6)'s call.

I've zapped you some old fashioned Sats, they're not as ...

2026-11-02T11:28:31Z

In reply to nevent1q…6pwh
_________________________

I've zapped you some old fashioned Sats, they're not as popular as they once were, but I'm sure you'll find a use for them 😂

Remember, these vicious killers are direct descendants of wolves. ...

2026-11-02T11:28:16Z

Remember, these vicious killers are direct descendants of wolves.

Fuck that shit, I am sorry. I have my limits 🤣😂

2026-11-02T11:26:50Z

In reply to nevent1q…vtwz
_________________________

Fuck that shit, I am sorry. I have my limits 🤣😂

CALVIN KLEIN DOUBLE BUN BREAD. Someone said next time add ...

2026-11-02T11:26:48Z

CALVIN KLEIN DOUBLE BUN BREAD.

Someone said next time add chocolate filling to it. 😆

Craig's coin, to the moon 🚀 ...

2026-11-02T11:25:28Z

In reply to nevent1q…qzpc
_________________________

Craig's coin, to the moon 🚀

https://coinmarketcap.com/currencies/bitcoin-sv/

Nostr event nevent1qqsxydxs6435426mwz77x9jjlnvs7fa7g26alf4hehcj9v9l008uksgpr4mhxue69uhkxmmjv3hzuen9v4j8xtnjv4kxz7fww3hk7mrnqgsy07tafc9xgry2jc7nlfcanu9x4tv43ta9qhl0mmwk65577sfzaucuw7gch

2026-11-02T11:21:09Z

The root of unhappiness is desire. The uprooting of unhappiness ...

2026-11-02T11:23:13Z

In reply to nevent1q…02kh
_________________________

The root of unhappiness is desire. The uprooting of unhappiness is...

WTF is BSV? 🤣😂

2026-11-02T11:22:41Z

In reply to nevent1q…ueqm
_________________________

WTF is BSV? 🤣😂

Putting this on my Christmas list. 🤣😂 ...

2026-11-02T11:22:40Z

Putting this on my Christmas list. 🤣😂

I so want to make a joke about "Wen BSV?" 😂

2026-11-02T11:22:04Z

In reply to nevent1q…stmu
_________________________

I so want to make a joke about

"Wen BSV?" 😂

Correction to the comment above, after reading `ChatScreen` ...

2026-11-02T10:57:07Z

In reply to naddr1qq…s3jy
_________________________

Correction to the comment above, after reading `ChatScreen` properly. **Both "product calls" dissolve, so neither needs an answer** — the defaults I proposed there are superseded by this.

Two things in the screen that the earlier reading missed:

- `unreadLanding(entries, mark)` (`ChatScreen.kt:440`) needs the unread divider to be inside whatever is loaded. A window that is simply "the newest N" lands a chat with more unread than N in the wrong place.
- `searchMatches` (`:537`) matches the **sender's display name** as well as the message text, through `session.label(it, profiles)`. No SQL `LIKE` over `content` can reproduce that, so "the find bar searches the store" was not a default I could have implemented as stated.

What replaces both: **the window's floor drops to the bottom of the chat whenever something deliberate asks for it.** Opening the find bar drops it to zero for as long as the bar is open. A permalink, a reply's jump or a pin's jump to a row below the floor drops it, then jumps. That is today's behaviour exactly, at today's cost, paid only when a person asks for it — and the read the issue is actually about, the one that runs on every arriving message and every chat open, is the one that shrinks. No new search path, no new wording, and nothing for anyone to decide on either count.

The rest of the shape:

- `AccountSession.timeline(gid)` takes a floor. The flow reads `cursor >= floor`, and the `Timeline` carries `hasMore` — which is `Message.sq:countBelow`, already written for the prune.
- The opening floor is the **lower** of the Nth-newest cursor (`selectNthNewestCursor`, also already there and also callerless) and one above the read mark, so every unread row is loaded and the landing still finds its divider. An account with four hundred unread in a chat pays for four hundred rows on opening it, which is the right answer for that person and still not the whole history.
- Scrolling within a page of the top lowers the floor by a page.
- The top of the list gains its third state, which remains the defect most likely to come out of this: "more to load" while `hasMore`; `PrunedHistoryNote` when `hasMore` is false and `group.pruned`; nothing otherwise. Never inferred from `rows.size`.
- A reply's quoted line and the pin banner need the target's *text*, not its position in the list, so they take a store lookup by event id (`messageByEventId`, indexed) and leave the floor where it is. Only an actual jump moves it.

Three of the reads this needs are already in `Message.sq` and two of them have never had a caller.

Nostr event nevent1qqsp7cma95d2tp6ndc7mvmztvn3xasqwpnjry6w5a4hrj5yx46sazwqpr4mhxue69uhkxmmjv3hzuen9v4j8xtnjv4kxz7fww3hk7mrnqgsvmmxrr3kegphf5lttqpn5z24xv8vax8yqxhpl6ewqvvqarjkrhysdwnga9

2026-11-02T10:49:58Z

In reply to nevent1q…uy7e
_________________________

https://thumb.wikimedia.org/wikipedia/commons/thumb/1/16/Motorola_RAZR_V3i_01.JPG/1280px-Motorola_RAZR_V3i_01.JPG?utm_source=en.wikipedia.org&utm_campaign=index&utm_content=thumbnail

First half landed: merge commit `0c225d55`, tip `0d265207`. The ...

2026-11-02T10:55:17Z

In reply to naddr1qq…s3jy
_________________________

First half landed: merge commit `0c225d55`, tip `0d265207`. The three notifiers now read the rows above the chat's read cursor instead of the whole history, and the counter at the SQL driver reads 7 rows per arriving message at 100, 1,000 and 5,000-row chats, against 100, 1,000 and 5,000 before. Walked on a phone, six steps, including a reaction to a message below the window — the one a naive window would have deleted silently.

This issue stays open for the other half: the chat screen's own windowing, whose design is in the comment above.

## The two product calls, and what I am building under

Nobody has settled them, and leaving the issue parked on an unanswered question is worse than building under a default and saying so. Both defaults are the same principle — **a window must not change what a person can reach, only when it is fetched** — so neither puts new wording in front of anyone:

1. **The find bar searches the whole stored history, not the loaded window.** It says "only what this device holds" today and that stays true: the search goes to the store rather than over the loaded rows. A window that quietly narrowed search results would be a regression nobody asked for, and it is the one of the two that could lose a person a message they know is there.

2. **A permalink, a reply's target and a pin below the loaded window load it, and only the prune floor says anything.** The window fetches older rows until the row is there and then jumps to it, exactly as today. The "gone for good" wording stays reserved for `group_.pruned_below_cursor`, which is the only case where it is true. So the screen gains no second kind of bad news — the third state at the top of the list ("more to load") is a loading affordance, not a message about missing history.

If either default is wrong, it is cheaper to say so now than after the screen is rebuilt: cloud fodder (nprofile…juxr) and rosie (nprofile…3pn6).

GM!

2026-11-02T10:55:03Z

In reply to nevent1q…xmxt
_________________________

GM!

Merged into `main` at `0c225d55768f9fc24d3cd247f75ab38ea48dff38`, ...

2026-11-02T10:53:41Z

In reply to naddr1qq…s3jy
_________________________

Merged into `main` at `0c225d55768f9fc24d3cd247f75ab38ea48dff38`, tagged `v0.1.30-pre.48` (`preview: a chat's notification costs the unread count instead of reading the whole history`). `main` = `staging` = `0c225d55`.

**The merge.** Tested tip `0d265207` was the branch tip on the relay and `main` (`7c0459d3`) was its ancestor, so nothing came in with the merge and no step is in question. `--no-ff` as policy, a merge commit either way. CHANGELOG is not in the diff, so no placement and no clash: nothing a person can see changes here.

**Condition 12 (0.1.30-pre.34) is the live condition this diff reaches, and it is NOT spent.** `DesktopChrome.kt` and `WebNotifier.kt` are both in it. 12 asks for a reaction notification walked on each of those surfaces — the desktop over a session that can raise one, a browser with permission granted — and both arms are still shut by this box rather than by any change (#bb1f6daf).

**No new condition, and the reason is the narrowing.** The two declared carries are those files' one-line call sites. Read against the tree, each is byte-identical to the Android line walked in full: `session.unreadRowsNow(gid, g.lastReadCursor)` against Android's `session.unreadRowsNow(gid, group.lastReadCursor)`, the local name the only difference. The callee is shared commonMain code, executed by the handset walk and counted by `NotifierReadCostTest`, and the lookup the window made necessary was driven by Verify 5 on the phone. So what is left dark is two call sites on two surfaces — which is exactly what condition 12 names, and a walk that satisfies 12 drives these lines in passing. One condition covering two landings' worth of dark code is the right answer; a fourteenth asking for the same walk would not be a second check.

Every other live condition is absent from the diff. `AccountSession.kt` is in it, which is where condition 7's post-pull hook lives, but the hunks are at 735-770 and the hook is `fetchMissingPackImages` at 1499-1501, in no hunk, and none of `EmojiPackSync`, `EmojiPackDoc` or `TipDocTransport` is present — 7 stands. `ShareScreen` absent, so 3 and 8 stand; `AccountRepairScreen`, `NetworkReturnWorker`, `deploy/flatpak`, the key-import host and the landing repository absent, so 1, 2, 4, 5 and 6 stand; `PackEmojiSender` and the sticker path absent, so 10 stands; `RetentionService` and `AccountStore.vacuum()` absent, so 13 stands.

**The two corrected steps are corrections, not carries**, and the superseding comment is the record for both. Step 1's day separator was pushed out of reach by another run filling that chat to 830 rows, and `chat-scroll.yaml` does not assert one anyway; the step as walked — whole history, scroll back until "Jump to latest", scroll forward until it goes — is the step's substance, and `ec61ad6d timeline: 830 rows` with `timeline on screen 224 ms after opening (828 rows)` is better evidence for it than a separator would have been. Step 2's "within a few seconds" is a promise about delivery, not about this change: it was walked on the documented background path and the delivery behaviour is filed on its own.

**#8d0d1303 is deliberately put back to open, in-progress.** This landing is its first half; the merge resolved it automatically and that is not the truth of it. The chat screen's own windowing, its paging story and the two product calls for cloud fodder (nprofile…juxr) all sit on that issue, and pr-sash is still working it, so the issue stays open until the second half lands.

Nostr event nevent1qqs9xptakyqaj0tzuzrv0g247z6p9ewt064avx5e0evkec66l3rv0rqpr4mhxue69uhkxmmjv3hzuen9v4j8xtnjv4kxz7fww3hk7mrnqgsy07tafc9xgry2jc7nlfcanu9x4tv43ta9qhl0mmwk65577sfzaucqq4mha

2026-11-02T11:15:58Z

GM For those that seek privacy: #nevent1q…6snk

2026-11-02T11:20:42Z

GM

For those that seek privacy:

quoting
nevent1q…6snk
There's a major state sponsored misinformation and smear campaign towards GrapheneOS in the Netherlands and Germany. The misinformation campaign includes unsubstantiated security claims not holding up to scrutiny to scare people away from it. They're also heavily misrepresenting who uses it overall.

💩🤡

2026-11-02T11:19:18Z

In reply to nevent1q…0g6x
_________________________

💩🤡

Real estate. Country lake in Virginia. 2.5 hours from ...

2026-11-02T11:10:47Z

Real estate.

Country lake in Virginia. 2.5 hours from Raleigh/Durham, 4.5 hours from DC,

800 homes for sale. a quick scroll shows prices from 300 to 1 million.

For the privilege of looking out at this lake, you can pay 7000 per 100,000 borrowed. so if you borrowed let's say 500,000 for a pretty nice place, these sellers expect you to be able to pay $35000/year or ~$3000 per month (just interest) alone.

or perhaps you just have $500,000 laying around and think that a view of this Virginia lake is worth that much. I don't know anyone who can afford that. literally anyone. and they are expecting that 800 people can afford that around 1 lake.

If you have the Tesla M40 24GB With 24GB of VRAM, you have ...

2026-11-02T11:06:20Z

If you have the Tesla M40 24GB

With 24GB of VRAM, you have roughly 22GB of usable space. This unlocks a massive tier of capability, allowing you to run 14B to 32B models, or run smaller 8B models at pristine unquantized/high-quantization levels.
• Qwen 2.5 14B Instruct
• File Size: ~9.3 GB (Q4_K_M) or ~16GB (Q8_0).
• Memory Footprint: ~13 GB to 20 GB depending on your selected quantization.
• Performance: Sits comfortably in the middle of your 24GB ceiling. The 14B parameter count offers a massive jump in reasoning, logic depth, and nuance compared to 8B variants.
• Mistral Large 2 (Instruct 123B) - Down-Quantized
• Alternative Target: If you want a deep reasoning model, you can squeeze a 32B model or a highly compressed Q2_K version of a larger model into 22GB. However, for a 24GB card, running Qwen 2.5 14B at 8-bit quantization (Q8_0) yields the absolute best balance of speed and flawless intelligence on old hardware.

Because the Tesla M40 computes FP16 instructions at a crawl, you must use quantized GGUF models running via standard CPU/GPU offloading backends like llama.cpp or Ollama. These frameworks run completely independently of TensorFlow, executing quantized integer math (INT4/INT8) perfectly on older CUDA cores.

f you have the Tesla M40 12GB

With 12GB of VRAM, you have roughly 10.5GB to 11GB of usable space after accounting for backend software overhead and context windows. Your targets are 7B to 8B parameter models quantized down to 4-bit (Q4_K_M).
• Llama 3.1 8B Instruct
• File Size: ~4.7 GB (Q4_K_M quantization).
• Memory Footprint: ~7.5 GB to 9.5 GB (including an 8k context window buffer).
• Performance: Fits completely into your 12GB VRAM pool. It is an exceptional general-purpose model for coding, logical reasoning, and everyday chat tasks.
• Qwen 2.5 7B Instruct
• File Size: ~4.7 GB (Q4_K_M quantization).
• Memory Footprint: ~8.0 GB to 10.0 GB total system overhead.
• Performance: Highly optimized for structured outputs (like generating JSON), mathematics, and coding scripts. It performs similarly to or better than Llama 3.1 8B on technical tasks.
f you have the Tesla M40 12GB

Nostr event nevent1qqsr35z9r64p3uh6g7xrrn6mptukyafkgq6p220jghu4ksy0vx7qvyqpr4mhxue69uhkxmmjv3hzuen9v4j8xtnjv4kxz7fww3hk7mrnqgsvmmxrr3kegphf5lttqpn5z24xv8vax8yqxhpl6ewqvvqarjkrhysdt0zvg

2026-11-02T10:37:51Z

so you need a pixel phone to run graphene OS? why is that?

Device run at tip `0d265207`, on raven, debug build md5 ...

2026-11-02T10:48:57Z

In reply to naddr1qq…s3jy
_________________________

Device run at tip `0d265207`, on raven, debug build md5 `b8fc5d30eb5a7fd63722169279e07b5d` installed over `02246fee295a5f8d9d20a73a16f7952f`; one staircase package at both ends, and the phone's delivery setting put back as it was found. All six Verify steps observed. **Two steps are corrected below; this comment supersedes the body's wording for them.**

## What each step showed

**1. Nothing on screen moved.** `maestro --device <serial> test .maestro/flows/chat-scroll.yaml -e CHAT='nym-rig' -e NONCE=093742` — every command COMPLETED: the run's own message sent, twelve screens back until it left the screen with "Jump to latest" raised, fourteen forward until it came back and the button went. The app's own line on opening that chat reads `ec61ad6d timeline: 830 rows, store 53 ms, build 24 ms`, then `timeline on screen 224 ms after opening (828 rows)` — the whole history, still read whole, which is the point of the step.

**Correction to step 1.** The published wording names the day separator for 24 October. That chat has since been filled to 830 rows by another run, so twelve screens of scrolling reach 1 November and the separator is far beyond any reasonable walk; `chat-scroll.yaml` does not assert a day separator either, and says in its own header why it stopped doing so (#120b2f2a). The step as walked is: open the long chat, expect its whole history, scroll back until the newest message leaves the screen and "Jump to latest" appears, scroll forward until it returns. Observed, and the row count above is the stronger evidence for what the step is about.

Steps 2 to 6 ran in a fresh rig room with a desktop install of this same tip as the second member, because the older rig chat's ingestion refuses every new message on this phone (`Moved past a message sealed with keys this group does not use (a member's client is out of step)` at cursors 1072-1074 — that install's MLS state for that room is out of step with the group, which has nothing to do with this change and does not touch a local timeline read).

**2. A message while away.** Notification raised with `android.title = sash-rig: Sash Caller` and `android.text = sash-step2 are you coming to the thing tonight`, on the `messages` channel at importance 4, category `msg`. The right sender, the right text.

**3. Three in a row, not the history.** Two more sent while still backgrounded: one notification for the chat, `android.messages` a bundle of **3**, `android.text` the newest line, `ONLY_ALERT_ONCE` set so it updated silently. Three unread in a chat then holding eight rows.

**4. Read it, then one more.** Chat opened (which marks it read), backed out, backgrounded, one message sent: `android.messages` a bundle of **1**, `android.text = sash-step4 just this one`. Exactly what sits above the read mark, nothing below it.

**5. A reaction to something you wrote long ago.** The target was a message of the phone account's own, six rows below the read mark and read long before. The second member reacted with 🔥, and the notification read `android.title = sash-rig: Sash Caller`, `android.text = reacted 🔥 to your message`. This is the step this change could have broken silently: the message reacted to is outside the window, and it was found through the `message_event_id` lookup.

**6. Reading it clears it.** Opening the chat took its notification out of the shade (three matching records before, none after).

**Correction to step 2's timing.** The published step says "within a few seconds". That is what Instant delivery gives, and it is not what this run could observe. On this phone today, with Instant selected, its foreground-service notification up and the coordinator streams exchanging ping and pong every 30 s, a message published by another member did not arrive while the app was in the background — eight minutes with nothing, then it landed the instant the app was foregrounded, stamped with the time it had actually been sent. Steps 2 to 6 were therefore walked with the phone on Frequent (five-minute alarm), the documented background path, and the notifications arrived 455 s, 497 s, 1 s and 295 s after their events. The step's substance — that the notification is raised and says the right thing — is observed; its promise about *how soon* is not, and is not something this change touches either way. The delivery behaviour is filed on its own.

## Declared carries, unchanged

`DesktopChrome.kt:161` and `WebNotifier.kt:73` were declared carried in the body and stay carried: this box raises no notification at all (#bb1f6daf), so neither notifier's output can be read here. Both lines are the same call Android makes, walked in full above.

## Checks, for the record

Gate at this tip, `BUILD SUCCESSFUL in 5m 10s`: `:cordn-store:jvmTest :app-core:jvmTest :cordn-sync:jvmTest :ui:jvmTest :app-desktop:compileKotlin :app-android:compileDebugKotlin`. Web, `BUILD SUCCESSFUL in 6m 24s`: `:cordn-store:wasmJsBrowserTest :app-core:wasmJsBrowserTest :app-web:wasmJsBrowserTest :app-web:e2e`, with `all 152 checks passed in 229s`. Rows the database hands out per arriving message, counted at the driver: 7 at 100, 1,000 and 5,000-row chats, against 100, 1,000 and 5,000 before.

Some on the ground puppetry ...

2026-11-02T10:44:24Z

Some on the ground puppetry

https://www.youtube.com/watch?v=cRsHgO9KKF0

a NOSTR native #nevent1q…krkr

2026-11-02T10:43:30Z

a NOSTR native

quoting
nevent1q…krkr
19X World Champion.
Every major title.

✅ Strikeforce
✅ Invicta FC
✅ UFC
✅ Bellator MMA
✅ PFL

yassis what a queen! 😍

2026-11-02T10:42:09Z

In reply to nevent1q…u4md
_________________________

yassis what a queen! 😍

Nostr event nevent1qqsxjzhumvx7y7tmws3juef6dthtezt3e5haapwn2dxdespc7760u3cpr4mhxue69uhkxmmjv3hzuen9v4j8xtnjv4kxz7fww3hk7mrnqgsvmmxrr3kegphf5lttqpn5z24xv8vax8yqxhpl6ewqvvqarjkrhys697u7z

2026-11-02T10:41:20Z

isn;'t black friday coming around soon?

https://i.nostr.build/nb5069.gif

2026-11-02T10:36:33Z

In reply to nevent1q…lnms
_________________________

OMG why can't i be there with you in the cold rn She's ...

2026-11-02T10:33:39Z

OMG why can't i be there with you in the cold rn

She's waking up to like -3 or something 😍

this too shall pass!

2026-11-02T10:36:33Z

In reply to nevent1q…lzuh
_________________________

this too shall pass!

Dick-measuring fights between avid Pedos be like 🥱 ...

2026-11-02T10:36:14Z

Dick-measuring fights between avid Pedos be like 🥱

just start

2026-11-02T10:36:04Z

In reply to nevent1q…c4ft
_________________________

just start

Nostr event nevent1qqsqa46vetzp95pyqkt8snue65pkq6npakuz92rq3aq056a5ued70cgpr4mhxue69uhkxmmjv3hzuen9v4j8xtnjv4kxz7fww3hk7mrnqgsvmmxrr3kegphf5lttqpn5z24xv8vax8yqxhpl6ewqvvqarjkrhys0z24k0

2026-11-02T10:29:17Z

nostrich is back

it's actually insane how close my GTA character looks like ...

2026-11-02T10:25:52Z

it's actually insane how close my GTA character looks like this guy

what a degen

quoting
nevent1q…xstc

wife?

2026-11-02T10:30:07Z

In reply to nevent1q…hxx6
_________________________

wife?

She was the first officer, not the pilot in control. The ...

2026-11-02T10:31:02Z

In reply to nevent1q…6c4g
_________________________

She was the first officer, not the pilot in control.

The horizontal stabiliser had completely separated.

They didn't stand a chance.