LWB on Nostr: LibreNostr 0.1.4 is out. This one is about speed. Opening a reply from your ...
LibreNostr 0.1.4 is out. This one is about speed.
Opening a reply from your notifications used to walk the thread's ancestor chain one relay round trip at a time, up to five, then make three or four more in sequence. Ten sequential round trips, each paying its own timeout. NIP-10 already names a reply's root and parent in its e tags, so the whole ancestor set fits in a single filter. It's three rounds now, and the first one is the note you opened together with its replies, so what you're actually looking at is never queued behind anything else.
The feed no longer polls every 30 seconds. It keeps a live REQ open on the people you follow, so a new note shows up about a second after it's published instead of up to half a minute later, and nothing goes out to the relays while nothing is happening. There's still a slow refresh underneath, because a subscription can die quietly and a feed that stops updating without telling you is worse than one that updates late.
Nostr events are immutable and content-addressed, so an event you already have on disk is the same event. Thread ancestors and the notes behind a notification are usually already there from the feed, and they aren't downloaded twice any more. Profile metadata is deduplicated per session rather than forever, so someone changing their display name still comes through.
And a full page of results no longer waits for the slowest relay. Every query used to pay a grace period after the first EOSE and, when that EOSE was empty, wait out the slowest relay — even when the first one had already delivered everything asked for. That early exit only fires on a full page, never a partial one, so a fast relay with a single event still can't hide the rest of the network.
Also fixed: tagged users render as the name they chose instead of an ellipsized npub, and follow notifications are grouped by day rather than piled under one row covering every follower you've ever had.
Get it here
https://zapstore.dev/apps/com.librenostr.androidPublished at
2026-09-01 14:23:47 CESTEvent JSON
{
"id": "53c0736c8dc3470ca15c76df8c3e6b5e640064bb8e4c74d780486965dbf13669",
"pubkey": "648c0f5302c75f38382a4d2c85a482b927cc61b2828a0794e36c6cc796de86a6",
"created_at": 1788265427,
"kind": 1,
"tags": [],
"content": "LibreNostr 0.1.4 is out. This one is about speed.\n\nOpening a reply from your notifications used to walk the thread's ancestor chain one relay round trip at a time, up to five, then make three or four more in sequence. Ten sequential round trips, each paying its own timeout. NIP-10 already names a reply's root and parent in its e tags, so the whole ancestor set fits in a single filter. It's three rounds now, and the first one is the note you opened together with its replies, so what you're actually looking at is never queued behind anything else.\n\nThe feed no longer polls every 30 seconds. It keeps a live REQ open on the people you follow, so a new note shows up about a second after it's published instead of up to half a minute later, and nothing goes out to the relays while nothing is happening. There's still a slow refresh underneath, because a subscription can die quietly and a feed that stops updating without telling you is worse than one that updates late.\n\nNostr events are immutable and content-addressed, so an event you already have on disk is the same event. Thread ancestors and the notes behind a notification are usually already there from the feed, and they aren't downloaded twice any more. Profile metadata is deduplicated per session rather than forever, so someone changing their display name still comes through.\n\nAnd a full page of results no longer waits for the slowest relay. Every query used to pay a grace period after the first EOSE and, when that EOSE was empty, wait out the slowest relay — even when the first one had already delivered everything asked for. That early exit only fires on a full page, never a partial one, so a fast relay with a single event still can't hide the rest of the network.\n\nAlso fixed: tagged users render as the name they chose instead of an ellipsized npub, and follow notifications are grouped by day rather than piled under one row covering every follower you've ever had.\n\nGet it here\n\nhttps://zapstore.dev/apps/com.librenostr.android",
"sig": "3aec2aa8efebdcc773215246e7b24bc99eb4bf86c34bd1a7ec3a42b4b17477831130b822d7c65fe043fa3a1ca492afbb99d532614abbbe2d970f932a8a51eec2"
}
