LibreNostr 0.2.6 is out. Quoted notes often showed "Mentioned event not found" — the field that used to carry them was Primal's centralized cache server's job, never replaced with a relay fetch after the fork. The thread screen and main feed now ask relays for a missing quoted note directly. Also fixed: the new Accounts entry in Settings opened empty, a bunker (NIP-46) account could get prompted for leftover event kinds Amber was already shielded from, and a cancelled bunker connection could leak an open socket.

GitHub

Release LibreNostr v0.2.6 · Lwb89dev/librenostr

A quoted note that wasn't already cached for some other reason showed "Mentioned event not found", the new Accounts entry in Settings had nothing i...

Jesus this hits to close it hurts. Fuck the EU, may it collapse from within.

LibreNostr 0.2.0 is out. Added a request coordinator so screens stop independently asking relays for the same follow lists and profiles. This will smooth out your experience using the app. Also fixed: feeds losing events past ~4 relays, follow-bot notification spam, and live feed updates that used to re-fetch everything instead of just what's new. Update's already available, get it from @Zapstore or via Obtanium from github

GitHub

Release LibreNostr v0.2.0 · Lwb89dev/librenostr

A request coordinator so the app stops asking relays the same question twice, and three bugs it turned up along the way: direct messages showing ra...

now i am kinda mad that the monero guys have this amazingly fast client >:(

Monero Hallway

1...2...3...

@Schlaus Kwab @Biro Bela ooookay there's no way you guys did not plan this

LibreNostr 0.1.5 is out. Feeds, notifications and DMs were losing events past ~4 relays: the socket flow was unbuffered, so one slow collector blocked every relay behind it, and queries finished on the first EOSE. Buffered now, and a query waits for a quorum instead of a winner. Follow/unfollow bots (HiveMind, Tzongocu, Football whateverwasitsname) were flooding notifications. Not a spam problem — a key problem: a kind 3 list is republished in full on every change, so each cycle carries a new event id, and rows were keyed by event id. One account, seven identical rows in a minute. Follows are keyed by who and what day now. Plus: notifications and DMs fetched at session start, old DMs backfilled, an undo countdown before a note goes out, and a relay list rebuilt by probing instead of by reputation. Get the new release on @Zapstore as usual or from github:

GitHub

Release LibreNostr v0.1.5 · Lwb89dev/librenostr

Reliability with more than a handful of relays, a session that fetches before you go looking, and a notifications tab that stops shouting. Fixed Fe...

It's cool what @fiatjaf did. Monero folks asked for a client and he delivered in a couple of days one of the smoothest web client one could ask for. Kudos to the guy.

Monero Hallway

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

Zapstore

LibreNostr — Zapstore

Relay-first Nostr client for Android. Fork of Primal, without Primal cache servers as a requirement.

Peach fell to Swiss regulations, long live Peach.

I love how this environment is evolving so fast. View quoted note →

LibreNostr 0.1.3 is out. Actually de-Googled now. Play Billing, ML Kit, Cronet and Firebase are gone, but the interesting one is what survived the first pass: Google Play Services was still being pulled in transitively by the Breez Spark SDK, through credentials-play-services-auth. That wallet backend was already disabled in code and returning a stub, so it cost 17.8 MB of native code per ABI and the whole play-services auth stack for nothing. APK went from 78.6 MB to 55.2 MB. Primal Premium is gone too: 138 files, 14,742 lines that could not work without their servers anyway. Three privacy fixes: 1. Photos are stripped of metadata before they reach a Blossom server. A camera shot carries EXIF with GPS to a few metres, capture time, device make and serial, often the owner's name. Byte-level rewrite for JPEG, PNG and WebP, so pixels are copied untouched and nothing is re-encoded. Now LibreNostr deletes everything before sending them the a Blossom server. 2. Direct message queries no longer go to the hardcoded public fallback relays. Opening the messages tab used to tell seven third-party relay operators your pubkey and that you were reading DMs, whatever relays you had configured. 3. Long-form feeds fell back to the global firehose whenever the author list came out empty, and the public long-form firehose is mostly spam and pr0n. Reads now come from your follows, widened at most to their follows. Never global. Also in 0.1.3: notifications are faster and no longer truncated (one REQ instead of five, with each kind no longer competing for the same page), zaps are credited to whoever actually zapped rather than to the recipient's LNURL server, and NIP-84 highlights finally work with Amber, which was rejecting kind 9802 locally before the signer was ever asked. github.com/Lwb89dev/librenostr Get it on @Zapstore as usual