Nostr notes by

No. I just didn't thought about it on every app I made. But I ...

2026-09-04T22:38:00Z

In reply to nevent1q…0q2u
_________________________

No. I just didn't thought about it on every app I made. But I will look at what I can deploy as nsite further so that it appears in 44billion's app store.

Btw, in the app store, the author of an nsite isn't clickable, at least not on mobile. When you try, it always wants to open the app instead of going to the creator page.

I totally forgot that @npub1fa0…0z97 has that turned on by ...

2026-09-04T16:41:40Z

In reply to nevent1q…qwhn
_________________________

I totally forgot that nostrvault (npub1fa0…0z97) has that turned on by default!

No I don't do anything special between phases.

2026-09-04T00:12:53Z

In reply to nevent1q…kaps
_________________________

No I don't do anything special between phases.

@nprofile…urav Question about 44billion.net: Is this like a ...

2026-09-03T22:52:42Z

arthurfranca (nprofile…urav) Question about 44billion.net: Is this like a place where nsites can be installed in an app-like manner, and the app store contains only nsites? I found even apps of mine in the app store.

The Nostrich run returns when Carl returns.

2026-09-03T22:48:20Z

In reply to nevent1q…e52r
_________________________

The Nostrich run returns when Carl returns.

Nostr is a protocol, not a platform. But you are mostly right.

2026-09-03T22:23:00Z

In reply to nevent1q…e8pu
_________________________

Nostr is a protocol, not a platform. But you are mostly right.

GM! I am putting a GIF keyboard in @npub1fa0…0z97

2026-09-03T11:41:09Z

GM! I am putting a GIF keyboard in nostrvault (npub1fa0…0z97)

Cool to see @nprofile…2wzn self signing on @nprofile…gsu4

2026-09-03T06:23:09Z

Cool to see Qlango (nprofile…2wzn) self signing on Zapstore (nprofile…gsu4)

The largest @nprofile…radp simulation group on a single ...

2026-09-02T20:21:54Z

The largest White Noise (nprofile…radp) simulation group on a single computer with many virtual machines is at around 200 members, without a fork!

Things are getting slow at that scale, so we're working on speed improvements and it's not a real test in production on different phones, but quite encouraging numbers.

Nostr Compass #38 is out. Here is what changed across Nostr this ...

2026-09-02T18:28:24Z

Nostr Compass #38 is out. Here is what changed across Nostr this week:

Welcome back to Nostr Compass, your weekly guide to Nostr.

This week: Voca Voca (npub17h9…3hpu) 1.0 brings verified Nostr notes and long-form subscriptions to an offline Android reader that speaks articles aloud, nostream (maintainer: Cameri 🦦 (npub1a5r…g39a)) expands relay-side job routing and authenticated operation, NDK for Dart (maintainer: PABLOF7z (npub1l2v…ajft)) (maintainer fmar: fmar (npub1xpu…5ams)) fixes negentropy and multi-relay request lifetimes, Divine Mobile (maintainer rabble: rabble (npub1wmr…g240)) makes wrapped-message deletion and signing deterministic, Conduit Relay ConduitMarket (npub1nkf…2svu) protects gift-wrap inboxes by default, Amethyst amethyst (npub142g…xrj0) ships portable highlights, and Mostro Mostro (npub1m0s…40un) verifies signed orders before its spam gate. Napstr (maintainer Ben Arc: Ben Arc (npub1c87…8avm)) publishes audio catalogues and seeder heartbeats over Nostr while transferring files through Tor. Releases cover MDK and pakstr; protocol work merges an NIP-67 pagination hint and an NIP-84 highlight tag scheme in the NIPs repository while Nostr Wallet Connect adds transaction totals; and the NIP Deep Dive traces reposts and reactions across their event shapes and current implementations.

Read the full issue:

quoting naddr1qv…75e2

Welcome back to Nostr Compass, your weekly guide to Nostr.

This week: Voca Voca (npub17h9…3hpu) 1.0 brings verified Nostr notes and long-form subscriptions to an offline Android reader that speaks articles aloud, nostream (maintainer: Cameri 🦦 (npub1a5r…g39a)) expands relay-side job routing and authenticated operation, NDK for Dart (maintainer: PABLOF7z (npub1l2v…ajft)) (maintainer fmar: fmar (npub1xpu…5ams)) fixes negentropy and multi-relay request lifetimes, Divine Mobile (maintainer rabble: rabble (npub1wmr…g240)) makes wrapped-message deletion and signing deterministic, Conduit Relay ConduitMarket (npub1nkf…2svu) protects gift-wrap inboxes by default, Amethyst amethyst (npub142g…xrj0) ships portable highlights, and Mostro Mostro (npub1m0s…40un) verifies signed orders before its spam gate. Napstr (maintainer Ben Arc: Ben Arc (npub1c87…8avm)) publishes audio catalogues and seeder heartbeats over Nostr while transferring files through Tor. Releases cover MDK and pakstr; protocol work merges an NIP-67 pagination hint and an NIP-84 highlight tag scheme in the NIPs repository while Nostr Wallet Connect adds transaction totals; and the NIP Deep Dive traces reposts and reactions across their event shapes and current implementations.

Top Stories

Voca 1.0 reads verified Nostr notes and subscriptions aloud on Android

Voca is an offline Android reader that speaks articles, PDFs, Markdown files, and Nostr notes in the phone's own text-to-speech voice while the spoken sentence stays lit on the page. Its 1.0 release, published on 2026-08-27 under its own project key, makes Nostr a first-class source: paste a note address, an event identifier, an npub, a profile, or an ordinary web link with a Nostr entity inside it, and the app decodes the reference, fetches the signed event from relays, and reads the author's text rather than the web page built around it.

Two verified behaviors define the Nostr integration, both described in Voca's signed 1.0 announcement. First, every fetched event is checked against its recomputed id and its BIP-340 Schnorr signature before it is persisted, using the bootstrap relays, the author's NIP-65 relay list (a signed, replaceable kind 10002 event where an author lists the relays they read and write), and hints carried inside the reference itself, so a relay can decline to answer but cannot put words in an author's mouth. Second, adding an author's npub puts their NIP-23 long-form articles (addressable kind 30023 posts with titles, summaries, and images) into a single on-device inbox beside RSS and Atom feeds. The 1.1.0 update, announced on 2026-08-28 and published to Zapstore Zapstore (npub10r8…t2p8) on 2026-08-29, puts sentence-level scrolling on time, smooths long documents, and recovers the home-screen widget after manual scrolling, resizing, process restarts, and upgrades.

nostream expands relay-side DVM routing and authenticated operation

After August 19's job-ingestion work, nostream, a TypeScript relay implementation, stores and serves NIP-89 application handler events. NIP-89 (application handler discovery) uses kind 31989 recommendations and kind 31990 handler information, both already in the parameterized-replaceable range, so a client can query those kinds and receive a replacement when a d tag collides. The relay does not publish handler information for its own workers.

Pending NIP-90 (data vending machine) jobs now reach a worker process and return as result events. On success the relay signs a kind 6000-6999 result with its own key. A timeout or worker crash marks the job failed instead of leaving it submitted.

Authenticated sessions and admin HTTP calls sit on different boundaries. NIP-42 (client authentication to relays) tracks the authenticated pubkey per socket, can require AUTH before clients publish events, and advertises that requirement in the NIP-11 (relay information) document, with both controls off by default. Separately, admin API routes can accept NIP-98 signed HTTP authorization. NIP-98 (HTTP authentication with signed events) stays off until an operator enables it and names the allowed pubkeys.

NDK for Dart fixes negentropy, multi-relay request lifetimes, and signature verification

A NIP-77 (negentropy set-reconciliation) run in NDK, a Dart development kit for Nostr, returned the wrong have and need sets without erroring, because the codec did not speak negentropy protocol v1. The v1 encoding fix now returns the ids held by the relay and the ids it still needs.

Identical filters sent to different relays were collapsing into one request. Requests with the same filter now stay distinct when they target different relays or have different lifetimes, so a short query cannot mix another relay's events into the result or leave a live subscription stalled.

The same kit verifies a signature once and keeps that result. A later duplicate delivery no longer spends another check or overwrites the stored verified event.

Divine Mobile makes wrapped direct-message deletion and signing deterministic

Wrapped NIP-09 (event deletion request) kind 5 events that targeted a message never applied in Divine Mobile, a mobile short-video client that publishes through Nostr. The client now resolves each deletion against the named message instead of treating anything that is not a reaction as already processed. A second delete-for-everyone request while the first was still in flight used to vanish with no error and no kind 5 on the wire; concurrent deletes now each publish.

After the previously covered 1.0.22 release, sending the same 1:1 NIP-17 (gift-wrapped private DMs) text twice in one second built one rumor id, so the second send disappeared; each send now carries a token inside the NIP-59 (gift wrap) rumor so the ids differ.

A caller that had already signed a kind 4 or kind 5 event kept that signature, instead of having a client tag appended afterward, which changed the id and made relays reject the event as invalid.

Conduit Relay hardens its NIP-42 protected inbox

Kind 1059 gift wraps are stored for one recipient. Conduit Relay, a Go relay that keeps those wraps in a recipient-protected inbox, defaults to enforce mode: a kind 1059 query must present NIP-42 authentication as that recipient, or the relay rejects the request. Mixed-kind filters, wildcards, counts, and negentropy over those wraps are restricted, so another AUTH cannot turn them into a dump of someone else's inbox.

The same protected-inbox merge requires a canonical event id on the transmitted AUTH event and accepts an otherwise-valid NIP-42 event whether or not content is empty. Challenge-only still offers AUTH without blocking the read; disabled admits freely. The library default is enforce.

Amethyst ships NIP-84 highlights and fixes two relay-facing failure paths

Following last week's Blossom authorization work, Amethyst, an Android Nostr client, ships v1.14.0 with NIP-84 (portable highlights). A selected passage becomes a kind 9802 event from the composer, a highlights feed, or a share into the app.

The release adds NIP-29 channel deletion and archival controls (PR #3812) and measures relay behavior through the traffic the client already makes, then extends those NIP-66 probes with streaming, read, write, and URL checks (PR #3836, PR #3857). Amethyst also removes a SharedKeyCache hash-collision vulnerability and compares message-authentication codes in constant time (PR #3833), repairs a race that could lose connect-time AUTH delivery (PR #3838), stripes subscription-state locking to end an ANR convoy (PR #3851), and compares every subscription filter instead of only the first (PR #3856).

Newsletter #36 covered these relay-authentication, backup, and public-chat changes previously; v1.14.0 has now shipped them together. Concord soft bans close authority gaps found by an audit (PR #3885). Relay authentication has a redesigned permission flow (PR #3899), waits for challenge resolution instead of timing out (PR #3905), defaults new accounts to authenticate (PR #3931), honors that preference on relays outside the account's normal set (PR #3937), and keeps session grants across reconnects (PR #3955). A guided first-run and Settings flow makes key backups discoverable (PR #3909), Cashu proof backfill and history paging stop wallet balances from being truncated (PR #3941), and public chats can now be muted (PR #3939).

After that tag, trusted lists in kinds 30392 through 30395 are NIP-50 (full-text search) indexed by title only, so a list named in prose can be found without indexing member hex ids. Wallet refusals that arrived over NIP-47 (Nostr Wallet Connect) now show their error instead of looking like a tap that did nothing, including QUOTA_EXCEEDED and RESTRICTED, plus a timeout when the wallet never answers.

Mostro validates signed orders before expensive work and preserves order audit events

After v0.18.1's Cashu escrow foundation, Mostro, a peer-to-peer exchange daemon that coordinates orders over Nostr, tagged v0.18.5, which defaults transport to NIP-44 (payload encryption) and keeps gift wrap as an explicit opt-in.

The release anchors waiting-state timeouts to the recorded take time so a maker bond is not slashed on the wrong clock (PR #879), dispatches each settled-order buyer payout at most once (PR #881), and moves those payouts through bounded, non-blocking send_payment waits (PR #883). An attempted change to pay the timeout-slash winner (PR #875) was reverted before the same tag shipped (PR #885). Mostro also stops republishing an unchanged pending order book every hour and at startup (PR #888), and its kind 38386 dispute events now carry a created_at tag for downstream ordering (PR #878).

After that tag, a signature check now runs before the spam gate. An event id does not commit to sig, so a copy of a victim's kind 14 with a broken signature could occupy the replay slot and silently drop the valid message; the daemon verifies first and drops an invalid wrap instead of warning and continuing.

Fee-audit events of kind 8383 were carrying a NIP-40 (expiration timestamp) of 15 days. They now keep a one-year expiration, matching their role as a public payment record. On a Cashu-enabled node, taking an order asks the seller over Nostr to lock a 2-of-3 escrow, publishes the waiting order event, and skips creation of a Lightning hold invoice. That completes the request path; it does not by itself close every escrow or marketplace-abuse case.

Napstr publishes audio catalogues on Nostr and transfers files over Tor

Napstr is a desktop audio-sharing client that publishes searchable catalogues and live seeders on Nostr, then transfers the files through a bundled Tor process with no direct-IP fallback. Version 0.2.0 keeps profiles and catalogue metadata public, and it keeps requests, transfer credentials, file contents, and peer IP addresses off the relays.

Discovery uses two addressable event kinds in the Napstr repository. Kind 30421 catalogue entries name a file by its SHA-256 digest, public basename, size, and audio format, and an author withdraws a file by replacing that coordinate with a deleted marker. Kind 30422 availability heartbeats expire after ten minutes and list the file IDs the author is prepared to seed, so a catalogue row is live only while an unexpired heartbeat still contains that digest.

Public conversation uses NIP-C7 (kind 9 chat messages) instead of a relay-owned group. The Napstr repository defines a shared public room plus a per-track discussion keyed to the file digest. Those messages are signed and public. They do not carry onion addresses, transfer credentials, or file bytes.

A download starts as a NIP-17 (gift-wrapped private DMs) negotiation. The Napstr repository wraps a request, an offer, or a refusal inside a kind 14 rumor, so relays do not see the temporary v3 onion hostname or the one-use capability that an accepted offer returns. Bundled Tor then moves the bytes over that onion, verifies the complete SHA-256 digest, and re-validates the audio before the file becomes playable.

The v0.1.7 to v0.2.0 comparison adds audiobook collections and Napstrfy, an optional Android companion. Kind 30423 manifests list ordered chapters that remain ordinary catalogue files, so a client that ignores the collection can still fetch each chapter. Napstr creates a non-destructive local Audiobooks folder for that purpose. Napstrfy pairs to a running desktop with a one-use QR code, then searches and requests downloads through that desktop's existing Nostr and Tor services without receiving the desktop secret key.

The same comparison times out a companion handshake that does not complete. A seeder copies and hashes the shared file before it serves bytes, writes incoming data into a private temporary file, confines audiobook destinations to a real child of the Napstr folder, and aborts if that destination changes during the transfer.

Releases

MDK v0.9.17: newest KeyPackages, membership activity, and durable sends

Newsletter #37 covered MDK 0.9.14 and 0.9.15, including the change in the MDK repository from oldest-first KeyPackage selection to the newest valid current-profile package, the epoch-gap recovery gates, account cleanup, and the split between discovery and operational relays. Those fixes remain the base for the two releases that followed, so a stale package no longer blocks a member who has already published a usable one.

Membership and admin events now advance the chat list the way a new message does: preview text, ordering, unread counts, and read markers update when people join, leave, or change roles, and the local system actor is not treated as a Nostr profile. Reconnects and restarts reuse one send identity for a retried durable outbound text, so the same group message is not published twice.

The two releases since then concentrate on the cost of keeping large groups healthy. Version 0.9.16 measures epoch divergence from the current epoch rather than a high-water mark, keeps refused inbound events fetchable (PR #1565), scopes replay rollback to canonical group state (PR #1563), and introduces marmot-c, a macro-generated C ABI over the UniFFI bindings that lets hosts embed the engine directly. Version 0.9.17 then folds pass-admission scans into one member walk instead of a pass per member, probes whether a group state is contested without seeding the full history graph, cuts the deferred-peel sweep's idle-poll cost, and applies the batched component read to the three projection sites the first pass missed. The matching marmot-c 0.9.17 and WN Agent 0.9.17 artifacts are built from the same commit, so embedders get the cheaper maintenance paths together.

pakstr v0.16.0: kind-32267 identifiers on publish

After last week's 0.13.0 through 0.15.0 Zapstore publication pipeline, pakstr, a CLI that packages a web app into a signed Android APK and publishes it with a Nostr key, logs the kind 32267 application-event IDs it looks up, publishes, or replaces. Version 0.16.0 prints both the previous and new IDs when stale listing metadata triggers a republish, so a publisher can confirm which listing event is live on the relay.

The same identifier log records the ID found during lookup before any replace, then the ID of the event that landed, so a no-op reuse appears as a repeated ID. That is the tagged change in 0.16.0; the Content-Digest, publish-before-upload, and publisher-validation behavior already shipped in the earlier tags.

Unreleased Changes

Zap Cooking scopes bunker relays and signs paid endpoints

Reloading a bunker session on Zap Cooking ZapCooking (npub1xxd…kt7a), a recipe site built on Nostr long-form events, used to publish the encrypted NIP-46 (remote signing over relays) conversation to every relay the page already used. Scoping signer traffic to the bunker's own relays now applies that restriction on session restore and on nostrconnect pairing, the signer-initiated connection flow, matching the bunker-URL login path. It refuses to install an empty relay set from a malformed stored record, so relays that only host recipes no longer learn that the same pubkey keeps an active bunker session.

Signed HTTP authentication now gates the paid cooking-assistant chat, the cookbook introduction, and gated-recipe updates under NIP-98 (HTTP authentication with a signed Nostr event). The server reads the request body once, verifies the signature against that exact payload, and takes identity from the verified auth event instead of a public key supplied in the body. The chat preview still works with no header, while a present but invalid signature is rejected and the cookbook introduction always requires a signature. Updating a gated recipe now also requires that the verified key match the stored author; anyone else is told the recipe does not exist, so the endpoint does not confirm which paid records exist.

nostrord repairs wrapped DMs and shared event links

After last week's v2.9.0, nostrord Nostrord (npub1ktx…zc2h), a cross-platform client for relay-hosted communities, merged delivery fixes so a NIP-17 (gift-wrapped private DM) sent from one device reaches the same account elsewhere. Publishing the sender's self-copy independently stops the recipient wrap's first relay acceptance from dropping the copy other devices fetch. That same change resends a wrap after NIP-42 (client authentication to relays) completes, and it marks the send successful on the first relay acceptance so one failing host cannot stall the rest. Retrying parked gift wraps that failed NIP-59 (gift wrap) decryption now happens on a timer, so a bunker that stays connected no longer leaves those messages mi... [truncated]

A NIP-C7 (kind 9 chat messages) reply repeats its parent as a leading NIP-19 (bech32-encoded entities) nevent pointer beside the q tag. Dropping that leading parent pointer when it opens the body and names the reply parent lets the row render as a single reply quote, while a pointer mid-body or a pointer that is the whole body still renders as a quote card. Quoted-event links now encode nevent with the author, kind, and the relay the quote was read from, so a NIP-29 (relay-managed groups) event shared into a DM can be fetched by another client instead of a bare note identifier that carries no lookup hints.

NIP Updates and Protocol Spec Work

Nostr Implementation Possibilities

Two specification merges landed in the core NIPs repository this week.

NIP-67 defines hints a relay can append to an EOSE (end of stored events) message so a client knows whether to keep paginating. The merged "auth" hint adds a third value beside finish and more: a relay may now signal that additional stored events could become visible if the user authenticates, and it must send the NIP-42 (relay authentication) AUTH challenge before the EOSE that carries the hint. The accompanying NIP-42 addition defines the same flow from the client side, so a client that receives an EOSE with auth already holds the challenge it needs to answer.

NIP-84 (portable highlights, the kind 9802 events Amethyst shipped support for above) merged a tag-scheme update: highlights may now tag their source with structured i tags per NIP-73 (external content identifiers) in addition to a/e tags for Nostr events and r tags for anything else, and quote highlights moved from a MUST to a SHOULD on rendering like a quote repost.

Nostr Wallet Connect

A list_transactions response can report how many transactions match the request, not how many rows the current page returned. Merged optional total_count on NWC-05 (the wallet-history extension) in the NWC extension repository adds that field to the response used with NIP-47 (encrypted remote wallet control over Nostr).

The commit that adds total_count documents it as an optional integer: the total number of transactions matching the request filters.

The commit that excludes pagination from the count states that this total excludes pagination, so it counts all matching transactions across every page.

NIP Deep Dive: Reposts and Reactions

A contact can put an existing note back in front of their followers, and they can attach a compact like, dislike, or emoji without writing a reply. NIP-18 (reposts) publishes that redistribution as its own signed event. NIP-25 (reactions) publishes the compact response as a separate signed event. Both remain draft optional files on the canonical repost specification and the canonical reaction specification: they are present in the NIPs repository and implemented by clients, while still labeled non-final.

Reposts (NIP-18)

Followers receive a signed pointer to a kind 1 text note someone already published when a client writes a kind 6 event. The repost specification sets kind to 6, puts the stringified JSON of that note in content (empty content is allowed and not recommended), requires an e tag whose value is the note's id and whose third entry is a relay URL where the note can be fetched, and says the event SHOULD also carry a p tag with the original author's pubkey. A repost of a NIP-70 (protected events) event SHOULD keep content empty so the protected payload is not copied into the new event.

A quote is a citation inside some other event, not a kind 6 wrapper. When a client mentions a NIP-21 (nostr: URI) nevent, note, or naddr, it must convert that mention into a q tag of the form ["q", "<event-id> or <event-address>", "<relay-url>", "<pubkey-if-a-regular-event>"]. Quote-repost tags keep those citations out of reply threads and let clients pull and count the quotes on a post.

Kind 6 is reserved for kind 1 notes. A kind 16 generic repost can wrap any event kind other than kind 1. It SHOULD include a k tag whose value is the stringified kind of the inner event. When that inner event is replaceable, the generic repost SHOULD add an a tag with the kind:pubkey:d-tag coordinate; if that a tag is absent, the repost targets one specific version and content must hold the full JSON string of that version. The generic-repost rules keep long-form, addressable, and other non-note events from being published as if they were kind 1.

The following kind 6 event is a live repost recovered from wss://relay.damus.io at assembly time (open the event):
{
  "kind": 6,
  "id": "73d8e64314d8b62426faeef5554a95d7d80065a61e0de17d1802e683a93d534a",
  "pubkey": "a60e79e0edad5100d7543b669e513dbc1c2170e8e9b74fdb8e971afd1e0e6813",
  "created_at": 1787768621,
  "tags": [
    [
      "e",
      "38980cd673ee16609dc87081d9f645c331d5a5a8b5b0d6c8147600ed29447976"
    ],
    [
      "p",
      "34d2f5274f1958fcd2cb2463dabeaddf8a21f84ace4241da888023bf05cc8095"
    ],
    [
      "client",
      "Primal iOS"
    ]
  ],
  "content": "{\"pubkey\":\"34d2f5274f1958fcd2cb2463dabeaddf8a21f84ace4241da888023bf05cc8095\",\"sig\":\"8c0271f7b438083ce491c391335598e0cbceee0758177cf98f7894531033cb5153704b01009590f3d4e9cdfadd5bbf73fc5eea54186fcbac6d30744e0e6c1cd6\",\"id\":\"38980cd673ee16609dc87081d9f645c331d5a5a8b5b0d6c8147600ed29447976\",\"tags\":[[\"r\",\"https:\/\/stacker.news\/items\/1555439\"],[\"client\",\"Damus\"]],\"created_at\":1787766056,\"content\":\"🚨 Attention CLN (Core Lightning) node runners 🚨\n\nhttps:\/\/stacker.news\/items\/1555439\",\"kind\":1}",
  "sig": "b6b97fa377cfdb651e2850f65f2ccb12ca0724c0de0fc0e39e9721f850abdfd31f5d5567517a51d988145c2a2de9ae9540b02eecf7352e554022870d5e8c64a5"
}
Its kind is 6, the e tag points to the reposted note, the p tag identifies that note's author, and content carries the original kind 1 event as stringified JSON. This relay-recovered event omits the relay hint that the NIP-18 specification marks as required, illustrating why readers and clients must validate real events and allow for producers that omit fields.

Reactions (NIP-25)

A post can collect signed likes, dislikes, and emoji without those marks entering the reply thread. The reaction specification defines that mark as a kind 7 event whose content MUST carry the reaction value. + or an empty string MUST be read as a like or upvote. - MUST be read as a dislike or downvote. An emoji or a NIP-30 (custom emoji) shortcode SHOULD NOT be read as a like or dislike, and a client MAY display that emoji on the post.

The target is in the tags, not inferred from content. There MUST be an e tag set to the target event id, and that tag SHOULD include a relay hint; extra e tags are not recommended, and if they appear the target id must be last. There SHOULD be a p tag for the target author, last if several p tags appear. An addressable target SHOULD also get an a tag with kind:pubkey:d-tag coordinates. The e and a tags SHOULD include relay and pubkey hints, the p tags SHOULD include relay hints, and a k tag MAY carry the stringified kind of the reacted event. Those tag rules let a client fetch the target and notify its author from the reaction event alone.

A client MAY put a single :shortcode: in content and one emoji tag that maps that shortcode to an image URL, following the custom-emoji reaction rules. If the target is not a native Nostr event, the reaction MUST be kind 17 and MUST carry NIP-73 (external content IDs) k and i tags, as in the external-content reaction rules. Kind 17 is a reaction to a website, podcast episode, or other external object. It is not a kind 7 event-to-event reaction and it is not a repost.

The following kind 7 event is a live reaction recovered from wss://relay.damus.io at assembly time (open the event):
{
  "kind": 7,
  "id": "45f71a8fdefb7ac4e86f64b800996ae47f66f1d9a15c0b22d1aa3a962d3dfe63",
  "pubkey": "0755cc2b972c3cbcae36913109c50b36b3fe110fa38a76dc37d1f01c5305496a",
  "created_at": 1787768605,
  "tags": [
    [
      "e",
      "519de32071d71bb2ab8b71a07e03eb9a256b6a59f9b08877b156c80966d5c320"
    ],
    [
      "a",
      "34236:5ab67f7d7fed4f781008c0ec0d26c8113f9fb46094a8346246c70c75e75db9fb:2ddda68516f4729d3ef55a1eb01fe028253393212493a34816ad8eb79f97a3b7"
    ],
    [
      "p",
      "5ab67f7d7fed4f781008c0ec0d26c8113f9fb46094a8346246c70c75e75db9fb"
    ],
    [
      "k",
      "34236"
    ],
    [
      "client",
      "Divine",
      "31990:d95aa8fc0eff8e488952495b8064991d27fb96ed8652f12cdedc5a4e8b5ae540:divine-mobile",
      "wss://relay.divine.video"
    ]
  ],
  "content": "+",
  "sig": "3c081756c7a73e2ee8aa10fadf3b5009390d5ac9a72078ba03701c42af91022ef275df7cb17724689a23dca4e29ff1a7cd5e3a24135d021983e2726a28b00b1e"
}
Its content is +, the conventional like from NIP-25. The e tag names the reacted-to event; the a tag adds its addressable coordinate; the p tag identifies its author; and the optional k tag records the target's kind as a string.

Current client implementations

Amethyst, an Android Nostr client, defines the repost event type and the reaction event type in its current protocol layer.

Snort, a web Nostr client, implements NIP-18 helpers that include quote-link tag handling and creates NIP-25 event-reaction tags.

Ditto, a combined Mastodon server and Nostr relay, publishes kind 16 generic reposts with a k tag and an a coordinate on addressable targets and applies kind 7 reaction semantics by treating the last e tag as the target event.

How They Work Together

A kind 6 or kind 16 event redistributes an existing event into the reposter's followers' feeds, either by embedding that event's JSON or by pointing at a replaceable coordinate. A q tag marks a quote inside some other event so thread reconstruction can count citations without treating the quoting event as a reply, which is the split drawn in the quote-repost section. A kind 7 event leaves the original event in place and attaches only the reaction value plus target tags, which is the contract in the reaction specification. Clients that fetch one pubkey therefore see that pubkey's reposts as new kind 6 or 16 events and that pubkey's opinions as kind 7 events on other people's posts.

Send a NIP-17 DM to share a project or news item through the Nostr Compass project.

Nostr Compass #38 is out. Here is what changed across Nostr this ...

2026-09-02T18:26:50Z

quoting naddr1qv…75e2

Welcome back to Nostr Compass, your weekly guide to Nostr.

This week: Voca Voca (npub17h9…3hpu) 1.0 brings verified Nostr notes and long-form subscriptions to an offline Android reader that speaks articles aloud, nostream (maintainer: Cameri 🦦 (npub1a5r…g39a)) expands relay-side job routing and authenticated operation, NDK for Dart (maintainer: PABLOF7z (npub1l2v…ajft)) (maintainer fmar: fmar (npub1xpu…5ams)) fixes negentropy and multi-relay request lifetimes, Divine Mobile (maintainer rabble: rabble (npub1wmr…g240)) makes wrapped-message deletion and signing deterministic, Conduit Relay ConduitMarket (npub1nkf…2svu) protects gift-wrap inboxes by default, Amethyst amethyst (npub142g…xrj0) ships portable highlights, and Mostro Mostro (npub1m0s…40un) verifies signed orders before its spam gate. Napstr (maintainer Ben Arc: Ben Arc (npub1c87…8avm)) publishes audio catalogues and seeder heartbeats over Nostr while transferring files through Tor. Releases cover MDK and pakstr; protocol work merges an NIP-67 pagination hint and an NIP-84 highlight tag scheme in the NIPs repository while Nostr Wallet Connect adds transaction totals; and the NIP Deep Dive traces reposts and reactions across their event shapes and current implementations.

Top Stories

Voca 1.0 reads verified Nostr notes and subscriptions aloud on Android

Voca is an offline Android reader that speaks articles, PDFs, Markdown files, and Nostr notes in the phone's own text-to-speech voice while the spoken sentence stays lit on the page. Its 1.0 release, published on 2026-08-27 under its own project key, makes Nostr a first-class source: paste a note address, an event identifier, an npub, a profile, or an ordinary web link with a Nostr entity inside it, and the app decodes the reference, fetches the signed event from relays, and reads the author's text rather than the web page built around it.

Two verified behaviors define the Nostr integration, both described in Voca's signed 1.0 announcement. First, every fetched event is checked against its recomputed id and its BIP-340 Schnorr signature before it is persisted, using the bootstrap relays, the author's NIP-65 relay list (a signed, replaceable kind 10002 event where an author lists the relays they read and write), and hints carried inside the reference itself, so a relay can decline to answer but cannot put words in an author's mouth. Second, adding an author's npub puts their NIP-23 long-form articles (addressable kind 30023 posts with titles, summaries, and images) into a single on-device inbox beside RSS and Atom feeds. The 1.1.0 update, announced on 2026-08-28 and published to Zapstore Zapstore (npub10r8…t2p8) on 2026-08-29, puts sentence-level scrolling on time, smooths long documents, and recovers the home-screen widget after manual scrolling, resizing, process restarts, and upgrades.

nostream expands relay-side DVM routing and authenticated operation

After August 19's job-ingestion work, nostream, a TypeScript relay implementation, stores and serves NIP-89 application handler events. NIP-89 (application handler discovery) uses kind 31989 recommendations and kind 31990 handler information, both already in the parameterized-replaceable range, so a client can query those kinds and receive a replacement when a d tag collides. The relay does not publish handler information for its own workers.

Pending NIP-90 (data vending machine) jobs now reach a worker process and return as result events. On success the relay signs a kind 6000-6999 result with its own key. A timeout or worker crash marks the job failed instead of leaving it submitted.

Authenticated sessions and admin HTTP calls sit on different boundaries. NIP-42 (client authentication to relays) tracks the authenticated pubkey per socket, can require AUTH before clients publish events, and advertises that requirement in the NIP-11 (relay information) document, with both controls off by default. Separately, admin API routes can accept NIP-98 signed HTTP authorization. NIP-98 (HTTP authentication with signed events) stays off until an operator enables it and names the allowed pubkeys.

NDK for Dart fixes negentropy, multi-relay request lifetimes, and signature verification

A NIP-77 (negentropy set-reconciliation) run in NDK, a Dart development kit for Nostr, returned the wrong have and need sets without erroring, because the codec did not speak negentropy protocol v1. The v1 encoding fix now returns the ids held by the relay and the ids it still needs.

Identical filters sent to different relays were collapsing into one request. Requests with the same filter now stay distinct when they target different relays or have different lifetimes, so a short query cannot mix another relay's events into the result or leave a live subscription stalled.

The same kit verifies a signature once and keeps that result. A later duplicate delivery no longer spends another check or overwrites the stored verified event.

Divine Mobile makes wrapped direct-message deletion and signing deterministic

Wrapped NIP-09 (event deletion request) kind 5 events that targeted a message never applied in Divine Mobile, a mobile short-video client that publishes through Nostr. The client now resolves each deletion against the named message instead of treating anything that is not a reaction as already processed. A second delete-for-everyone request while the first was still in flight used to vanish with no error and no kind 5 on the wire; concurrent deletes now each publish.

After the previously covered 1.0.22 release, sending the same 1:1 NIP-17 (gift-wrapped private DMs) text twice in one second built one rumor id, so the second send disappeared; each send now carries a token inside the NIP-59 (gift wrap) rumor so the ids differ.

A caller that had already signed a kind 4 or kind 5 event kept that signature, instead of having a client tag appended afterward, which changed the id and made relays reject the event as invalid.

Conduit Relay hardens its NIP-42 protected inbox

Kind 1059 gift wraps are stored for one recipient. Conduit Relay, a Go relay that keeps those wraps in a recipient-protected inbox, defaults to enforce mode: a kind 1059 query must present NIP-42 authentication as that recipient, or the relay rejects the request. Mixed-kind filters, wildcards, counts, and negentropy over those wraps are restricted, so another AUTH cannot turn them into a dump of someone else's inbox.

The same protected-inbox merge requires a canonical event id on the transmitted AUTH event and accepts an otherwise-valid NIP-42 event whether or not content is empty. Challenge-only still offers AUTH without blocking the read; disabled admits freely. The library default is enforce.

Amethyst ships NIP-84 highlights and fixes two relay-facing failure paths

Following last week's Blossom authorization work, Amethyst, an Android Nostr client, ships v1.14.0 with NIP-84 (portable highlights). A selected passage becomes a kind 9802 event from the composer, a highlights feed, or a share into the app.

The release adds NIP-29 channel deletion and archival controls (PR #3812) and measures relay behavior through the traffic the client already makes, then extends those NIP-66 probes with streaming, read, write, and URL checks (PR #3836, PR #3857). Amethyst also removes a SharedKeyCache hash-collision vulnerability and compares message-authentication codes in constant time (PR #3833), repairs a race that could lose connect-time AUTH delivery (PR #3838), stripes subscription-state locking to end an ANR convoy (PR #3851), and compares every subscription filter instead of only the first (PR #3856).

Newsletter #36 covered these relay-authentication, backup, and public-chat changes previously; v1.14.0 has now shipped them together. Concord soft bans close authority gaps found by an audit (PR #3885). Relay authentication has a redesigned permission flow (PR #3899), waits for challenge resolution instead of timing out (PR #3905), defaults new accounts to authenticate (PR #3931), honors that preference on relays outside the account's normal set (PR #3937), and keeps session grants across reconnects (PR #3955). A guided first-run and Settings flow makes key backups discoverable (PR #3909), Cashu proof backfill and history paging stop wallet balances from being truncated (PR #3941), and public chats can now be muted (PR #3939).

After that tag, trusted lists in kinds 30392 through 30395 are NIP-50 (full-text search) indexed by title only, so a list named in prose can be found without indexing member hex ids. Wallet refusals that arrived over NIP-47 (Nostr Wallet Connect) now show their error instead of looking like a tap that did nothing, including QUOTA_EXCEEDED and RESTRICTED, plus a timeout when the wallet never answers.

Mostro validates signed orders before expensive work and preserves order audit events

After v0.18.1's Cashu escrow foundation, Mostro, a peer-to-peer exchange daemon that coordinates orders over Nostr, tagged v0.18.5, which defaults transport to NIP-44 (payload encryption) and keeps gift wrap as an explicit opt-in.

The release anchors waiting-state timeouts to the recorded take time so a maker bond is not slashed on the wrong clock (PR #879), dispatches each settled-order buyer payout at most once (PR #881), and moves those payouts through bounded, non-blocking send_payment waits (PR #883). An attempted change to pay the timeout-slash winner (PR #875) was reverted before the same tag shipped (PR #885). Mostro also stops republishing an unchanged pending order book every hour and at startup (PR #888), and its kind 38386 dispute events now carry a created_at tag for downstream ordering (PR #878).

After that tag, a signature check now runs before the spam gate. An event id does not commit to sig, so a copy of a victim's kind 14 with a broken signature could occupy the replay slot and silently drop the valid message; the daemon verifies first and drops an invalid wrap instead of warning and continuing.

Fee-audit events of kind 8383 were carrying a NIP-40 (expiration timestamp) of 15 days. They now keep a one-year expiration, matching their role as a public payment record. On a Cashu-enabled node, taking an order asks the seller over Nostr to lock a 2-of-3 escrow, publishes the waiting order event, and skips creation of a Lightning hold invoice. That completes the request path; it does not by itself close every escrow or marketplace-abuse case.

Napstr publishes audio catalogues on Nostr and transfers files over Tor

Napstr is a desktop audio-sharing client that publishes searchable catalogues and live seeders on Nostr, then transfers the files through a bundled Tor process with no direct-IP fallback. Version 0.2.0 keeps profiles and catalogue metadata public, and it keeps requests, transfer credentials, file contents, and peer IP addresses off the relays.

Discovery uses two addressable event kinds in the Napstr repository. Kind 30421 catalogue entries name a file by its SHA-256 digest, public basename, size, and audio format, and an author withdraws a file by replacing that coordinate with a deleted marker. Kind 30422 availability heartbeats expire after ten minutes and list the file IDs the author is prepared to seed, so a catalogue row is live only while an unexpired heartbeat still contains that digest.

Public conversation uses NIP-C7 (kind 9 chat messages) instead of a relay-owned group. The Napstr repository defines a shared public room plus a per-track discussion keyed to the file digest. Those messages are signed and public. They do not carry onion addresses, transfer credentials, or file bytes.

A download starts as a NIP-17 (gift-wrapped private DMs) negotiation. The Napstr repository wraps a request, an offer, or a refusal inside a kind 14 rumor, so relays do not see the temporary v3 onion hostname or the one-use capability that an accepted offer returns. Bundled Tor then moves the bytes over that onion, verifies the complete SHA-256 digest, and re-validates the audio before the file becomes playable.

The v0.1.7 to v0.2.0 comparison adds audiobook collections and Napstrfy, an optional Android companion. Kind 30423 manifests list ordered chapters that remain ordinary catalogue files, so a client that ignores the collection can still fetch each chapter. Napstr creates a non-destructive local Audiobooks folder for that purpose. Napstrfy pairs to a running desktop with a one-use QR code, then searches and requests downloads through that desktop's existing Nostr and Tor services without receiving the desktop secret key.

The same comparison times out a companion handshake that does not complete. A seeder copies and hashes the shared file before it serves bytes, writes incoming data into a private temporary file, confines audiobook destinations to a real child of the Napstr folder, and aborts if that destination changes during the transfer.

Releases

MDK v0.9.17: newest KeyPackages, membership activity, and durable sends

Newsletter #37 covered MDK 0.9.14 and 0.9.15, including the change in the MDK repository from oldest-first KeyPackage selection to the newest valid current-profile package, the epoch-gap recovery gates, account cleanup, and the split between discovery and operational relays. Those fixes remain the base for the two releases that followed, so a stale package no longer blocks a member who has already published a usable one.

Membership and admin events now advance the chat list the way a new message does: preview text, ordering, unread counts, and read markers update when people join, leave, or change roles, and the local system actor is not treated as a Nostr profile. Reconnects and restarts reuse one send identity for a retried durable outbound text, so the same group message is not published twice.

The two releases since then concentrate on the cost of keeping large groups healthy. Version 0.9.16 measures epoch divergence from the current epoch rather than a high-water mark, keeps refused inbound events fetchable (PR #1565), scopes replay rollback to canonical group state (PR #1563), and introduces marmot-c, a macro-generated C ABI over the UniFFI bindings that lets hosts embed the engine directly. Version 0.9.17 then folds pass-admission scans into one member walk instead of a pass per member, probes whether a group state is contested without seeding the full history graph, cuts the deferred-peel sweep's idle-poll cost, and applies the batched component read to the three projection sites the first pass missed. The matching marmot-c 0.9.17 and WN Agent 0.9.17 artifacts are built from the same commit, so embedders get the cheaper maintenance paths together.

pakstr v0.16.0: kind-32267 identifiers on publish

After last week's 0.13.0 through 0.15.0 Zapstore publication pipeline, pakstr, a CLI that packages a web app into a signed Android APK and publishes it with a Nostr key, logs the kind 32267 application-event IDs it looks up, publishes, or replaces. Version 0.16.0 prints both the previous and new IDs when stale listing metadata triggers a republish, so a publisher can confirm which listing event is live on the relay.

The same identifier log records the ID found during lookup before any replace, then the ID of the event that landed, so a no-op reuse appears as a repeated ID. That is the tagged change in 0.16.0; the Content-Digest, publish-before-upload, and publisher-validation behavior already shipped in the earlier tags.

Unreleased Changes

Zap Cooking scopes bunker relays and signs paid endpoints

Reloading a bunker session on Zap Cooking ZapCooking (npub1xxd…kt7a), a recipe site built on Nostr long-form events, used to publish the encrypted NIP-46 (remote signing over relays) conversation to every relay the page already used. Scoping signer traffic to the bunker's own relays now applies that restriction on session restore and on nostrconnect pairing, the signer-initiated connection flow, matching the bunker-URL login path. It refuses to install an empty relay set from a malformed stored record, so relays that only host recipes no longer learn that the same pubkey keeps an active bunker session.

Signed HTTP authentication now gates the paid cooking-assistant chat, the cookbook introduction, and gated-recipe updates under NIP-98 (HTTP authentication with a signed Nostr event). The server reads the request body once, verifies the signature against that exact payload, and takes identity from the verified auth event instead of a public key supplied in the body. The chat preview still works with no header, while a present but invalid signature is rejected and the cookbook introduction always requires a signature. Updating a gated recipe now also requires that the verified key match the stored author; anyone else is told the recipe does not exist, so the endpoint does not confirm which paid records exist.

nostrord repairs wrapped DMs and shared event links

After last week's v2.9.0, nostrord Nostrord (npub1ktx…zc2h), a cross-platform client for relay-hosted communities, merged delivery fixes so a NIP-17 (gift-wrapped private DM) sent from one device reaches the same account elsewhere. Publishing the sender's self-copy independently stops the recipient wrap's first relay acceptance from dropping the copy other devices fetch. That same change resends a wrap after NIP-42 (client authentication to relays) completes, and it marks the send successful on the first relay acceptance so one failing host cannot stall the rest. Retrying parked gift wraps that failed NIP-59 (gift wrap) decryption now happens on a timer, so a bunker that stays connected no longer leaves those messages mi... [truncated]

A NIP-C7 (kind 9 chat messages) reply repeats its parent as a leading NIP-19 (bech32-encoded entities) nevent pointer beside the q tag. Dropping that leading parent pointer when it opens the body and names the reply parent lets the row render as a single reply quote, while a pointer mid-body or a pointer that is the whole body still renders as a quote card. Quoted-event links now encode nevent with the author, kind, and the relay the quote was read from, so a NIP-29 (relay-managed groups) event shared into a DM can be fetched by another client instead of a bare note identifier that carries no lookup hints.

NIP Updates and Protocol Spec Work

Nostr Implementation Possibilities

Two specification merges landed in the core NIPs repository this week.

NIP-67 defines hints a relay can append to an EOSE (end of stored events) message so a client knows whether to keep paginating. The merged "auth" hint adds a third value beside finish and more: a relay may now signal that additional stored events could become visible if the user authenticates, and it must send the NIP-42 (relay authentication) AUTH challenge before the EOSE that carries the hint. The accompanying NIP-42 addition defines the same flow from the client side, so a client that receives an EOSE with auth already holds the challenge it needs to answer.

NIP-84 (portable highlights, the kind 9802 events Amethyst shipped support for above) merged a tag-scheme update: highlights may now tag their source with structured i tags per NIP-73 (external content identifiers) in addition to a/e tags for Nostr events and r tags for anything else, and quote highlights moved from a MUST to a SHOULD on rendering like a quote repost.

Nostr Wallet Connect

A list_transactions response can report how many transactions match the request, not how many rows the current page returned. Merged optional total_count on NWC-05 (the wallet-history extension) in the NWC extension repository adds that field to the response used with NIP-47 (encrypted remote wallet control over Nostr).

The commit that adds total_count documents it as an optional integer: the total number of transactions matching the request filters.

The commit that excludes pagination from the count states that this total excludes pagination, so it counts all matching transactions across every page.

NIP Deep Dive: Reposts and Reactions

A contact can put an existing note back in front of their followers, and they can attach a compact like, dislike, or emoji without writing a reply. NIP-18 (reposts) publishes that redistribution as its own signed event. NIP-25 (reactions) publishes the compact response as a separate signed event. Both remain draft optional files on the canonical repost specification and the canonical reaction specification: they are present in the NIPs repository and implemented by clients, while still labeled non-final.

Reposts (NIP-18)

Followers receive a signed pointer to a kind 1 text note someone already published when a client writes a kind 6 event. The repost specification sets kind to 6, puts the stringified JSON of that note in content (empty content is allowed and not recommended), requires an e tag whose value is the note's id and whose third entry is a relay URL where the note can be fetched, and says the event SHOULD also carry a p tag with the original author's pubkey. A repost of a NIP-70 (protected events) event SHOULD keep content empty so the protected payload is not copied into the new event.

A quote is a citation inside some other event, not a kind 6 wrapper. When a client mentions a NIP-21 (nostr: URI) nevent, note, or naddr, it must convert that mention into a q tag of the form ["q", "<event-id> or <event-address>", "<relay-url>", "<pubkey-if-a-regular-event>"]. Quote-repost tags keep those citations out of reply threads and let clients pull and count the quotes on a post.

Kind 6 is reserved for kind 1 notes. A kind 16 generic repost can wrap any event kind other than kind 1. It SHOULD include a k tag whose value is the stringified kind of the inner event. When that inner event is replaceable, the generic repost SHOULD add an a tag with the kind:pubkey:d-tag coordinate; if that a tag is absent, the repost targets one specific version and content must hold the full JSON string of that version. The generic-repost rules keep long-form, addressable, and other non-note events from being published as if they were kind 1.

The following kind 6 event is a live repost recovered from wss://relay.damus.io at assembly time (open the event):
{
  "kind": 6,
  "id": "73d8e64314d8b62426faeef5554a95d7d80065a61e0de17d1802e683a93d534a",
  "pubkey": "a60e79e0edad5100d7543b669e513dbc1c2170e8e9b74fdb8e971afd1e0e6813",
  "created_at": 1787768621,
  "tags": [
    [
      "e",
      "38980cd673ee16609dc87081d9f645c331d5a5a8b5b0d6c8147600ed29447976"
    ],
    [
      "p",
      "34d2f5274f1958fcd2cb2463dabeaddf8a21f84ace4241da888023bf05cc8095"
    ],
    [
      "client",
      "Primal iOS"
    ]
  ],
  "content": "{\"pubkey\":\"34d2f5274f1958fcd2cb2463dabeaddf8a21f84ace4241da888023bf05cc8095\",\"sig\":\"8c0271f7b438083ce491c391335598e0cbceee0758177cf98f7894531033cb5153704b01009590f3d4e9cdfadd5bbf73fc5eea54186fcbac6d30744e0e6c1cd6\",\"id\":\"38980cd673ee16609dc87081d9f645c331d5a5a8b5b0d6c8147600ed29447976\",\"tags\":[[\"r\",\"https:\/\/stacker.news\/items\/1555439\"],[\"client\",\"Damus\"]],\"created_at\":1787766056,\"content\":\"🚨 Attention CLN (Core Lightning) node runners 🚨\n\nhttps:\/\/stacker.news\/items\/1555439\",\"kind\":1}",
  "sig": "b6b97fa377cfdb651e2850f65f2ccb12ca0724c0de0fc0e39e9721f850abdfd31f5d5567517a51d988145c2a2de9ae9540b02eecf7352e554022870d5e8c64a5"
}
Its kind is 6, the e tag points to the reposted note, the p tag identifies that note's author, and content carries the original kind 1 event as stringified JSON. This relay-recovered event omits the relay hint that the NIP-18 specification marks as required, illustrating why readers and clients must validate real events and allow for producers that omit fields.

Reactions (NIP-25)

A post can collect signed likes, dislikes, and emoji without those marks entering the reply thread. The reaction specification defines that mark as a kind 7 event whose content MUST carry the reaction value. + or an empty string MUST be read as a like or upvote. - MUST be read as a dislike or downvote. An emoji or a NIP-30 (custom emoji) shortcode SHOULD NOT be read as a like or dislike, and a client MAY display that emoji on the post.

The target is in the tags, not inferred from content. There MUST be an e tag set to the target event id, and that tag SHOULD include a relay hint; extra e tags are not recommended, and if they appear the target id must be last. There SHOULD be a p tag for the target author, last if several p tags appear. An addressable target SHOULD also get an a tag with kind:pubkey:d-tag coordinates. The e and a tags SHOULD include relay and pubkey hints, the p tags SHOULD include relay hints, and a k tag MAY carry the stringified kind of the reacted event. Those tag rules let a client fetch the target and notify its author from the reaction event alone.

A client MAY put a single :shortcode: in content and one emoji tag that maps that shortcode to an image URL, following the custom-emoji reaction rules. If the target is not a native Nostr event, the reaction MUST be kind 17 and MUST carry NIP-73 (external content IDs) k and i tags, as in the external-content reaction rules. Kind 17 is a reaction to a website, podcast episode, or other external object. It is not a kind 7 event-to-event reaction and it is not a repost.

The following kind 7 event is a live reaction recovered from wss://relay.damus.io at assembly time (open the event):
{
  "kind": 7,
  "id": "45f71a8fdefb7ac4e86f64b800996ae47f66f1d9a15c0b22d1aa3a962d3dfe63",
  "pubkey": "0755cc2b972c3cbcae36913109c50b36b3fe110fa38a76dc37d1f01c5305496a",
  "created_at": 1787768605,
  "tags": [
    [
      "e",
      "519de32071d71bb2ab8b71a07e03eb9a256b6a59f9b08877b156c80966d5c320"
    ],
    [
      "a",
      "34236:5ab67f7d7fed4f781008c0ec0d26c8113f9fb46094a8346246c70c75e75db9fb:2ddda68516f4729d3ef55a1eb01fe028253393212493a34816ad8eb79f97a3b7"
    ],
    [
      "p",
      "5ab67f7d7fed4f781008c0ec0d26c8113f9fb46094a8346246c70c75e75db9fb"
    ],
    [
      "k",
      "34236"
    ],
    [
      "client",
      "Divine",
      "31990:d95aa8fc0eff8e488952495b8064991d27fb96ed8652f12cdedc5a4e8b5ae540:divine-mobile",
      "wss://relay.divine.video"
    ]
  ],
  "content": "+",
  "sig": "3c081756c7a73e2ee8aa10fadf3b5009390d5ac9a72078ba03701c42af91022ef275df7cb17724689a23dca4e29ff1a7cd5e3a24135d021983e2726a28b00b1e"
}
Its content is +, the conventional like from NIP-25. The e tag names the reacted-to event; the a tag adds its addressable coordinate; the p tag identifies its author; and the optional k tag records the target's kind as a string.

Current client implementations

Amethyst, an Android Nostr client, defines the repost event type and the reaction event type in its current protocol layer.

Snort, a web Nostr client, implements NIP-18 helpers that include quote-link tag handling and creates NIP-25 event-reaction tags.

Ditto, a combined Mastodon server and Nostr relay, publishes kind 16 generic reposts with a k tag and an a coordinate on addressable targets and applies kind 7 reaction semantics by treating the last e tag as the target event.

How They Work Together

A kind 6 or kind 16 event redistributes an existing event into the reposter's followers' feeds, either by embedding that event's JSON or by pointing at a replaceable coordinate. A q tag marks a quote inside some other event so thread reconstruction can count citations without treating the quoting event as a reply, which is the split drawn in the quote-repost section. A kind 7 event leaves the original event in place and attaches only the reaction value plus target tags, which is the contract in the reaction specification. Clients that fetch one pubkey therefore see that pubkey's reposts as new kind 6 or 16 events and that pubkey's opinions as kind 7 events on other people's posts.

Send a NIP-17 DM to share a project or news item through the Nostr Compass project.

I downsized my homelab from 5 servers to 3 super powerful ones ...

2026-09-02T15:56:56Z

I downsized my homelab from 5 servers to 3 super powerful ones (and added an extra battery), so now a lil rain won't take out Ditto Relay anymore.

That was a dream, never got one myself, but helped a couple ...

2026-09-02T12:09:18Z

In reply to nevent1q…apmp
_________________________

That was a dream, never got one myself, but helped a couple friends set up theirs, fantastic idea.
Also interesting to have one flatbed truck and multiple shipping containers in different places to be flexible with moving them. That requires a big truck tho...

Have some fun while the tokens are cheap.

2026-09-02T15:15:51Z

In reply to nevent1q…u6r8
_________________________

Have some fun while the tokens are cheap.

GN from 🇱🇰 Nostriches! Life is not same for everyone. My ...

2026-09-02T15:14:40Z

GN from 🇱🇰 Nostriches!

Life is not same for everyone. My wish is to have at least 3 meals for every people and street animals. ❤️

See you tomorrow! 🙌

That would be ideal. Give people the tools to do it themselves, ...

2026-09-02T11:49:26Z

In reply to nevent1q…cafr
_________________________

That would be ideal. Give people the tools to do it themselves, choose their own storage, and if they don't have the skills, Apple or Google is always an option.

Very cool. Thank you for doing this.

2026-09-02T11:50:08Z

In reply to nevent1q…gy8y
_________________________

Very cool. Thank you for doing this.

Yes.

2026-09-02T10:01:48Z

In reply to nevent1q…es3n
_________________________

Yes.

To be fair, that's the cost of the initial buildout I did in ...

2026-09-02T10:01:35Z

In reply to nevent1q…yter
_________________________

To be fair, that's the cost of the initial buildout I did in a single week. It was very bare bones, basically wood, solar, battery, and hammock. No heater (other than candles) nor running water.
There were more costs in upgrades and fixes since then.

What holidays? anyhow, we talk marmot now, join us! ...

2026-09-01T16:00:37Z

What holidays?
anyhow, we talk marmot now, join us!

quoting
nevent1q…4ull
The holidays are over, but we’ve never stopped 💪

September is going to be a busy month full of EXCITING news. Stay tuned and see you today at Marmot community call at 16:00

Here: https://meet.fulmo.org/marmot

What a waste of time and money.

2026-09-02T01:06:22Z

In reply to nevent1q…9l6s
_________________________

What a waste of time and money.

There is a tool called AIFlow for the M5Stack devices. It only ...

2026-09-01T12:49:30Z

In reply to nevent1q…ct29
_________________________

There is a tool called AIFlow for the M5Stack devices. It only supports Anthropic-compatible endpoints, that's why I asked.

I have shown this to ChatGPT and here is what it thinks about ...

2026-09-01T05:56:17Z

In reply to nevent1q…su47
_________________________

I have shown this to ChatGPT and here is what it thinks about this:

The meme is funny because it captures the bureaucratic absurdity of the situation surprisingly well. 😄

I do think the basic idea behind the EU’s Digital Services Act makes sense: services with tens of millions of users can have major societal effects, so requiring transparency, risk assessments, independent audits and accountability is not unreasonable.

But the categories do not fit every modern service equally well.

Reddit being classified as a Very Large Online Platform makes perfect sense. It is almost the textbook definition of one: users publish content, others comment and vote, recommendation systems influence visibility, and the platform hosts huge public communities.

Roblox also fits the VLOP category reasonably well once you stop thinking of it as merely a video game. It is really a platform for user-created games and experiences, with social features, communication, recommendation systems and a massive creator ecosystem. Given how many children use Roblox, additional scrutiny is especially understandable there.

ChatGPT being classified as a Very Large Online Search Engine, however, feels much more like regulatory drawer-thinking.

Yes, ChatGPT can search the web. But it can also write text, explain mathematics, program, analyze files, translate, brainstorm, reason about problems and simply have conversations. Calling the whole service a “search engine” describes only one part of what it does.

Law needs categories, of course. The problem begins when a new kind of technology does not really fit the existing categories, so regulators squeeze it into the closest available drawer anyway.

That is why the meme works so well:
“We did it lads, we regulated.”

EU hat successfully placed the giant regulatory hat on the chatbot. 🇪🇺😂

So my view is basically:

Reddit as VLOP: very sensible. Roblox as VLOP: also quite sensible. ChatGPT as VLOSE: legally understandable, conceptually awkward.

Regulating very large AI services is not inherently a bad idea. But in the long run, generative AI assistants probably deserve a regulatory category that actually describes what they are, rather than pretending they are simply very large search engines.

I spent two weeks on a cruise ship getting the same question: why ...

2026-08-31T17:45:47Z

I spent two weeks on a cruise ship getting the same question: why does a social media company need Bitcoin?

Here's the whole answer. It has nothing to do with price charts.

Why Bitcoin: The Base Layer of Freedom Tech

https://soapbox.pub/blog/why-bitcoin-freedom-rail

Spoiler: I mentioned gladstein (npub1trr…hdpu) and Check Your Financial Privilege

Gooooood Morning Nostriches! 🌞 Another week is gonna start and ...

2026-08-30T19:56:38Z

Gooooood Morning Nostriches! 🌞

Another week is gonna start and the month is gonna end. In the early morning I would like to gladly let you know that your 91st Nostr Recap (31st August 2026) is out! 😍

In this Nostr Recap, you could explore what happened last week in the #Nostr world under the topics below. Enjoy it! 👀

🧠 Quote of the Week
🔥 Community Highlights
🌱 Ecosystem Growth
🎓 Educational Guides
📅 Upcoming Events
📰 Nostr in the Media
⚡ Most Zapped Last Week
😂 Nostr Memes
🛠️ Tools, Updates and Releases
🎁 Developer Tools, Updates and Releases
🧩 Workspace Updates and Releases
🚧 Infrastructure Updates and Releases

Explore here 👇🏻

quoting
naddr1qv…a49f

M✨️ (npub1xy0…pf8a)

“Goodmorning Nostr

Just a daily reminder that no one can shadowban your sunshine on Nostr! Let's propagate some positivity today! Keep your keys safe, your relays synced, and your spirit free.

Can’t wait to be ignored on an open protocol today. Zero algorithms. Pure chaos. The best part about Nostr is nobody can cancel you except your own personality. ☕️👌🍀🌞

First rule of Bitcoin. self-custody. First rule of Nostr. self-sovereignty. How did you end up down this rabbit hole, and what are you trying to accomplish here? Are you here to build, push pure signal, drop killer memes, or fight for the mission ? ?

Drop your story below ? 🫂💜✨️”

1. A significant loss for a winemaker 😥

nevent1q…a9x5

2. A nostrich asks for help from the Nostr community 👇🏻

nevent1q…h8ng

3. It is worth checking this out 😍

nevent1q…h82j

4. These kinds of incidents are so disappointing to the user 👇🏻

nevent1q…wd9t

5. Starting the day with this kind of Nostr note is so awesome ☕

nevent1q…jk64

6. A huge release from Roadstr 👇🏻

nevent1q…d2nx

7. Submissions have closed. Time to judge & reward 😍

nevent1q…tnf4

8. A Nostrich enjoyed his 34th birthday with his heritance 🎂

nevent1q…wxut

9. We need these kinds of inspirations for the growth of Nostr 👇🏻

nevent1q…nz6z

10. Nostr creator suggests a solution to fix reply spam 👇🏻

nevent1q…s2wy

The Nostr growth indicates differently in several sources!

According to https://github.com/aljazceru/awesome-nostr, there are over 240 Nostr clients and over 500 Nostr apps running in more than 40 countries around the globe now.

According to https://nostrhub.io/stats

👉🏻 1,035 relays on the Nostr network

Top 3 Popular Clients by Usage (For 7 days):

👉🏻 Amethyst - 2243 Users

👉🏻 Primal - 1671 Users

👉🏻 Ditto - 409 Users

According to https://nostrarchives.com/analytics

Top 3 Popular Clients by Usage (For 7 days):

👉🏻 Primal iOS - 803 Users - 7.5k Notes

👉🏻 Amethyst - 768 Users - 13.1k Notes

👉🏻 Primal Android - 522 Users - 4.3k Notes

Top 3 Popular Relays by Usage (by NIP-65 relay lists):

👉🏻 relay.primal.net - 296.0k Users

👉🏻 nos.lol - 277.8k Users

👉🏻 relay.damus.io - 269.1k Users

According to https://stats.andotherstuff.org/

👉🏻 Publishing Users last week: 4.65M (+5.0%)

👉🏻 New Publishing Users Last week: 4.53M (-0.6%)

👉🏻 All-time Zap Count: 7.05M

👉🏻 All-time Zap BTC Amount: 43.52 BTC

👉🏻 All-time Zap Senders: 181.0K

According to https://npub.world/stats

During last week:

👉🏻 Total Users: 7,858 users, compared to 10,741 users the week before

Many thanks to the developers of https://nostrhub.io/stats, https://nostrarchives.com/analytics, https://stats.andotherstuff.org/ by jeffg (npub1zuu…c2uc) https://npub.world/stats by pip (npub176p…vgup) and all the contributors of https://github.com/aljazceru/awesome-nostr for providing these insights.

1. Lesson 5: Security and privacy, Nos2x, NIP-05, changing relays

AreaBitcoin (npub13zp…p5ww)

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

2. Buzz replaces your git password with a signature from your own key

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

3. Buzz: 1 Free Workspace Where AI Agents Are Teammates

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

1. Nostr Atlanta #17 - Rush Hour Avoidance - September 2026

📅 Date: Wednesday, September 16, 2026 ⏰ Time: 4.30 PM - 6.00 PM (EDT) 📍 Location: 684 John Wesley Dobbs Ave NE suite a1, Atlanta, GA, United States 🤹‍♀️ Organizers: cluborange (npub1ve8…9ka6)

🔗 Event:

https://plektos.app/event/naddr1qvzqqqrukvpzqejwqu87yhnkmh8054yjnsx7gtk26zqspy6s0cjdu33zqagumda2qqvrvcfexvexxwrpvgmkvetrxc6xyvtyvfjnxcfcvcfl34sn

2. Munich Nostr Meetup (newbies & nerds welcome) - September 2026

📅 Date: Thursday, September 17, 2026 ⏰ Time: 10:00 PM - 2:00 AM (Event timezone is not specified) 📍 Location: Munich 🤹‍♀️ Organizers: Munich Nostr Meetup

🔗 Event:

https://plektos.app/event/naddr1qvzqqqrukvpzqhqmqsq4yn3q08xvk94w75spay4c0p9fzu290p8d5nwkpwgn3f98qqex6atwd93ksttwdaehgu3dd4jk2ar4wqkkuethvf5k2ueddejhyern94mk2mrrdakk2tf3xycxzeryxycqekle0a

3. NOSTRSHIRE - November 2026

📅 Date: Friday, November 20, 2026 ⏰ Time: 9.00 AM - 6.00 PM (GMT) 📍 Location: Pendulum Hotel, Sackville St, Manchester M1 3BB, United Kingdom 🤹‍♀️ Organizers: Nostrshire (npub14mu…r84r) Nathan Day (npub1cn6…wt8a)

🔗 Event:

https://bitfest.uk/#nostrshire

1. Derek Ross defines Nostr on X

https://x.com/derekmross/status/2092582888856301986

2. What the Heck Is Nostr? I Didn't Know Either

https://www.publish0x.com/skylords-bitcoin-lab/what-the-heck-is-nostr-i-didnt-know-either-xokydvq

3. Divine is bringing back six-second looping videos with a modern twist

https://t2online.in/tech/tech-news/remember-vine--divine-is-bringing-back-six-second-looping-videos-with-a-modern-twist/2007508

4. The Human Rights Foundation Announces Support for 16 Projects Worldwide (Some Nostr projects are also included)

https://bitcoinmagazine.com/news/human-rights-foundation-issues-more-grants

5. Vine-inspired video app Divine makes global debut, bans AI-generated content

https://www.exchange4media.com/industry-briefing-news/vine-inspired-video-app-divine-makes-global-debut-bans-ai-generated-content-157573.html

Nostr’s Value4Value (V4V) model is all about plebs directly rewarding creators for the value they receive, no middlemen fees, no ads, just pure community-driven support using sats via the Bitcoin Lightning Network.

Thanks to https://zaplife.lol by PABLOF7z (npub1l2v…ajft) for providing these insights.

Here are the Top Zapped/Top Zappers from last week, showcasing the creators who received/sent the most engagement:

🔥 Top 3: Most Zapped

Name: flash (npub1f4u…r407)

Zaps Received: 424

Sats Earned: 195k

Name: fountainboostbot (npub1hpn…tplc)

Zaps Received: 346

Sats Earned: 643k

Name: Ȼħ!łłꞤθⱳ𐏑 (npub1uwj…axfl)

Zaps Received: 138

Sats Earned: 7k

🔥 Top 3: Most Zappers

Name: aqstr (npub1dsn…2h64)

Zaps Sent: 1482

Sats Spent: 34k

Name: 匿名応援者

Zaps Sent: 167

Sats Spent: 1M

Name: Turkey (npub1vkd…9g2t)

Zaps Sent: 113

Sats Spent: 3k

💰 Top 3: Most Sats Received

Name: Blue

Sats Earned: 841k

Zaps Received: 13

Name: fountainboostbot (npub1hpn…tplc)

Sats Earned: 643k

Zaps Received: 346

Name: flash (npub1f4u…r407)

Sats Earned: 197k

Zaps Received: 426

💰 Top 3: Most Sats Sent

Name: 匿名応援者

Sats Spent: 1M

Zaps Sent: 167

Name: 7f766a7dfd7ea23ffc24c7b27da138e8d81d1d0b3ca45c5da1a10e9d0778f5dc (npub10am…j8tf)

Sats Spent: 100k

Zaps Sent: 3

Name: OB (npub1u0g…tkzz)

Sats Spent: 63k

Zaps Sent: 2

Here are the Top Zapped from last week, showcasing notes that received the most engagement:

🔥 Top 3: Most Zapped

nevent1q…hu4a

Zaps Received: 103

Sats Earned: 13k

nevent1q…trvu

Zaps Received: 63

Sats Earned: 36k

nevent1q…cdcl

Zaps Received: 40

Sats Earned: 3k

🔥 Top 3: Most Sats

nevent1q…9maj

Sats Earned: 55k

Zaps Received: 3

nevent1q…htfs

Sats Earned: 38k

Zaps Received: 1

nevent1q…trvu

Sats Earned: 36k

Zaps Received: 63

nevent1q…8vx3

nevent1q…fwjq

nevent1q…ef9x

nevent1q…vmpx

nevent1q…9wjs

nevent1q…k58p

nevent1q…wtqs

nevent1q…9pd8

nevent1q…y4ah

nevent1q…w52j

nevent1q…eam0

nevent1q…mf8u

nevent1q…yl20

nevent1q…rjxl

1. Livelier.live - New Tool

Livelier.live is a free, open-source Nostr-based tool that helps self-hosted live streamers get discovered when they go live. It bridges live streams to Nostr as NIP-53 live events while keeping the actual video on the streamer’s own server. It also enables two-way live chat without re-hosting or permanently storing stream content.

Developed by: Rod (npub1r0d…fsft) - Source: https://github.com/r0d8lsh0p/livelier

2. Communitator - New Tool

Communitator is a Nostr web application that helps community leaders create and share relay templates for new users. With one click, users can apply a template to automatically update their Nostr relay lists, Blossom servers, and DM relays.

Developed by: 𓆩sᴇᴛᴛᴏ𓆪 (npub18ug…20ex) - Source: https://git.basspistol.org/hq/Communitator

3. Earthly - v0.1.6

Earthly is a collaborative Nostr-based map editor that lets people turn local knowledge into useful, shared maps by creating and editing map entities together. This release makes chat and entity editing explicit, giving users clearer control over when they are communicating and modifying map content.

Contributed by: Schlaus Kwab - Source: https://github.com/zeSchlausKwab/earthly/releases/tag/v0.1.6

4. Jumble - v26.8.3

Jumble is a user-friendly Nostr client for exploring relay feeds, letting users browse Nostr content, interact with profiles and notes, manage notifications, and connect to relays. Its latest release improves relay reconnection reliability, link previews, Nostr reference handling, sign-in security, notifications, encryption key syncing, and desktop persistence.

Contributed by: daniel (npub1aeh…4nwx) - Source: https://github.com/CodyTseng/jumble/releases/tag/v26.8.3

5. YakiHonne Web - v6.0.1

Yakihonne Web is a decentralized social payment client built on Nostr and Bitcoin, combining social networking, publishing, paid content, and Lightning-based payments. The latest release improves the publishing and premium content experience, adds a dedicated pricing page, supports kind 1111 comments and replies, and fixes issues with the AI Assistant, Second Reader, comment threads, and profile editing.

Contributed by: Moos (npub19qc…7xw2) - Source: https://github.com/YakiHonne/web-app/releases/tag/v6.0.1

6. Nymchat - v3.75.543

Nymchat is a feature-rich, ephemeral geohash and Bluetooth mesh chat client built on Nostr and bridged with Bitchat for pseudonymous, temporary messaging. The latest release adds message threads across channels, private messages, and group chats, upgrades Nymbot Premium to post-quantum encrypted private messaging, and includes numerous bug fixes. This was the latest, and there were also a few more releases last week.

Contributed by: Luxas (npub16jd…33sv) - Source: https://github.com/Spl0itable/NYM/releases/tag/v3.75.543

7. WaveFunc - 0.1.11

WaveFunc Radio is a Nostr-based internet radio directory and player with full-text search capabilities, allowing users to discover and listen to radio stations through a decentralized platform. The latest release adds MusicBrainz lookups through Blossom while reducing relay bandwidth usage and strengthening production policies.

Contributed by: Schlaus Kwab - Source: https://github.com/zeSchlausKwab/wavefunc/releases/tag/v0.1.11

8. Mostro Mobile Client - v1.4.0

Mostro Mobile Client is a modern, secure mobile client for the Mostro peer-to-peer Bitcoin trading platform, enabling users to manage trades, invoices, orders, disputes, and Lightning payments. The latest release adds trusted communities for Argentina and Brazil, improves invoice availability and settled-order payouts, supports insecure WebSocket relays in debug builds, and includes several bug fixes for order handling, disputes, payments, and app reliability.

Contributed by: negrunch (npub1qqq…rfkq) Catrya (npub1cat…euhz) andreadcorreia (npub1zvy…vfj0) - Source: https://github.com/MostroP2P/mobile/releases/tag/v1.4.0

9. Nostur - v1.31.0

Nostur is a Nostr client for iOS and macOS that provides a feature-rich interface for browsing feeds, profiles, posts, replies, media, badges, live chats, and discovering content across Nostr relays. This release improves feed performance, media playback and discovery, badge management, live chat, private replies, post and thread loading, links and search, relay management, and spam filtering, while adding tools for importing and exporting blocked-account lists and managing Web of Trust settings.

Contributed by: Fabian (npub1n0s…lahe) - Source: https://github.com/nostur-com/nostur-ios-public/releases/tag/1.31.0

10. Nostrord - v2.10.0

Nostrord is a NIP-29 Nostr client focused on group conversations, direct messaging, and chat, allowing users to interact with Nostr groups and private communications across devices. This release improves DM navigation and message delivery, adds file attachment support across clients, introduces private groups, typed @mentions, better chat reactions and message handling, and fixes issues with notifications, quoted events, links, media, and Android performance.

Contributed by: Anjhc (npub1f27…9swu) char - Source: https://github.com/nostrord/nostrord/releases/tag/v2.10.0

11. NoorNote - v1.4.0

NoorNote is a Nostr client for the decentralized social protocol, offering social feeds, articles, messaging, profiles, zaps, and NIP-29 group interactions. The latest release adds personal Nostr analytics with post, engagement, follow, and zap statistics, improves article feeds and NIP-29 group chat displays, and fixes scrolling, timeline loading, DM notifications, and relay hints, while also bringing broader stability improvements through stricter linting and expanded automated testing.

Contributed by: alp (npub175n…g6w0) - Source: https://github.com/77elements/noornote/releases/tag/v1.4.0

12. Sidecar - v1.10.0

Sidecar is a Nostr keystore and signer that runs in your browser sidebar, providing secure identity and wallet management for Nostr applications. This release adds new themes, per-theme balance animations, bookmarks, improved notification handling for muted users, the PIN-change wallet fix, safer auto-pay requirements, clipboard invoice detection, Lightning address resolution when sending, and a dynamically sized bio editor.

Contributed by: daniel (npub1aeh…4nwx) - Source: https://github.com/dmnyc/sidecar/releases/tag/v1.10.0

13. Workstr Web - v2.0.0

Workstr Web is a static, local-first Nostr workout tracker PWA that helps users manage workouts, programs, recovery, and training history. The v2.0.0 release adds encrypted Nostr sync accounts and auto-backup, improved signer connections and recovery, more efficient encrypted backups, redesigned workout and recovery interfaces, improved workout history and program views, automatic PWA updates, and numerous sync and backup reliability fixes.

Contributed by: Workstr7blo, sette7blo - Source: https://github.com/Workstr7blo/workstr-web/releases/tag/v2.0.0

14. Roadstr - v0.5.0

Roadstr is an open-source, decentralized navigation app for Android built on the Nostr protocol. The v0.5.0 release adds an optional MapLibre-based 3D map engine with tilt and rotation, map styling, destination search, multi-stop routing, route alternatives, public transport itineraries, hazard alerts, turn-by-turn navigation, rerouting, and voice guidance, while keeping the original map renderer available. This was the latest, and there were also the releases of v0.4.29, v0.4.28 & v0.4.27 last week.

Contributed by: roadstrapp (npub1cwf…5mmc) Lwb89dev - Source: https://github.com/roadstrapp/roadstr-app/releases/tag/v0.5.0

1. Pakstr - New Developer Tool

Pakstr is an open-source tool that turns a web app into a signed, installable Android APK and publishes it to Zap Store in a single CI step. Using just a Nostr nsec, it handles APK signing and Zap Store authentication without requiring the Android SDK, Gradle, or manually managed keystores, making it simple to package and release web apps as Android applications.

Developed by: Freedom Tech Co. (npub1frd…h4dd) - Source: https://git.nostrdev.com/stuff/pakstr

2. Dart Nostr - v11.0.0 - Encrypted messaging, zaps, media & identity: everything a Nostr client needs

Dart Nostr is a production-grade Dart and Flutter SDK for building Nostr applications, providing developers with a complete toolkit for social clients, encrypted messaging, wallets, creator platforms, and other Nostr-based apps. Release v11.0.0 adds end-to-end encrypted messaging with group chats and file attachments, Lightning zaps and payments, decentralized media and file support, seed-phrase identity management, Nostr link handling, password-encrypted key backups, social features, relay authentication, and signer-agnostic key management, while also improving reliability, reconnection, caching, memory safety, and cross-platform support.

Developed by: Anas Fikhi - Source: http://github.com/anasfik/nostr/releases/tag/v11.0.0

3. NDK - v0.9.1

NDK (Nostr Development Kit) is a Dart library that enhances the Nostr development experience by providing developers with tools for relay connections, event handling, authentication, caching, subscriptions, and encryption. This release introduces major connection-management and reliability improvements, including better handling of authentication, reconnects, subscriptions, request replay, caching, and relay connectivity, while adding post-quantum hybrid encryption for direct messages using ML-KEM-1024 and binding connections to individual identities. It also includes breaking changes to relay connection handling and replaces the GPL-licensed Crystals-Dilithium implementation with FIPS 204 (ML-DSA).

Contributed by: frnandu, leo (npub1w9l…3tur) - Source: https://github.com/relaystr/ndk/releases/tag/v0.9.1

4. snow-actions/nostr - v2.0.0

snow-actions/nostr is a GitHub Actions developer tool that lets workflows create and publish Nostr events directly to Nostr relays, with support for automated event publishing and relay response handling. This release upgrades the runtime to Node.js 24 and modernizes the action’s JavaScript/ESM, bundling, dependencies, testing, linting, and WebSocket implementation. Although this was the latest of the week, there was also the release v1.9.0 last week.

Contributed by: SnowCait (npub1s02…fxtw) - Source: https://github.com/snow-actions/nostr/releases/tag/v2.0.0

No Relay Updates and Releases for last week.

No Protocol Updates and Releases for last week.

1. Buzz - v0.5.20

Buzz is a Nostr-based workspace where humans and AI agents can collaborate through a relay you own, combining messaging, projects, workflows, and agent-powered collaboration in a shared environment. The release v0.5.20 adds KLIPY GIF search to message composers and improves automatic mention handling, along with fixes to release attribution and CI workflows. This was the latest, and there was also the release of v0.5.19 last week.

Contributed by: Will Pfleger, Wes, klopez4212 - Source: https://github.com/block/buzz/releases/tag/desktop-v0.5.20

1. Lightning.Pub - v0.0.40

Lightning.Pub is a Nostr-native Lightning node that lets users connect and share Lightning nodes through Nostr identities with compatible applications. This release is a bug-fix release focused on improving liquidity-provider balance accounting, correcting provider recovery fee calculations after crashes, and fixing on-chain payment deduplication so multiple outputs in the same transaction are tracked correctly. The release requires no API, configuration, database migration, or manual migration changes. This was the latest and there was also the release of v0.0.39 last week.

Contributed by: shocknet_justin (npub1xvt…64sa) boufni95 - Source: https://github.com/shocknet/Lightning.Pub/releases/tag/v0.0.40

2. Originless - v1.0.2 - Lightweight standalone node (Nostr offloaded)

Originless is a multipurpose decentralized storage backend for apps, agents, pastebins, screenshots, and static sites, providing fast and reliable IPFS storage, pinning, anonymized media uploads, and gateway proxying. The latest release simplifies the node by removing built-in Nostr scraping, mirroring, and archiving in favor of a separate Nostr backup integration, while also cleaning up its API and telemetry, reducing dependencies, and streamlining its container setup. While this was the latest of the week, there were also the releases of v1.0.1 & v1.0.0 last week.

Contributed by: besoeasy (npub1hzn…l6zh) - Source: https://github.com/besoeasy/Originless/releases/tag/v1.0.2

No Nostr Exploration Tools releases for last week.

Nostr is built by plebs, for the plebs. If you found this Nostr recap helpful, consider supporting me, Nomishka, with a zap.

I’m committed to supporting Nostr, and I split a part of the zaps I receive for this note with the plebs mentioned in this recap for all their great effort. Thank you so much for being part of this journey. Let me know your thoughts about this Ninety First Nostr Recap & share your tips and suggestions for the next weekly #NostrRecap and let’s keep #GrowNostr together.

Thank you Jurjen de Vries (npub1l77…swft) for this amazing idea!

A big shoutout to rabble (npub1wmr…g240) for your generous patronage for my Nostr Recaps!

Thank you, my younger brother samalka (npub1nu5…hjyn) for helping me with the content and graphic stuff for my Nostr Recaps!

Recap by Nomishka (npub19hs…5jcn)

Zap Winners 🏆

🔥 Most Zaps Received - flash (npub1f4u…r407)

🔥 Most Zaps Sent - aqstr (npub1dsn…2h64)

💰 Most Sats Received - Blue

💰 Most Sats Sent - 匿名応援者

This Nostr Recap is built step by step with the content of the below Nostriches. Hats off to them for making Nostr alive. 🫡

M✨️ (npub1xy0…pf8a) BenJustman (npub153x…ryu8) laoc42 (npub1r30…t9ma) Derek Ross (npub18am…p424) Kip Ashlynn (npub1hsp…ly9q) Maria2000 (npub13kw…wg2a) roadstrapp (npub1cwf…5mmc) AlexNicol (npub1tjl…qs50) fiatjaf (npub180c…h6w6) jeffg (npub1zuu…c2uc) pip (npub176p…vgup) AreaBitcoin (npub13zp…p5ww) cluborange (npub1ve8…9ka6) Nostrshire (npub14mu…r84r) Nathan Day (npub1cn6…wt8a) PABLOF7z (npub1l2v…ajft) flash (npub1f4u…r407) fountainboostbot (npub1hpn…tplc) Ȼħ!łłꞤθⱳ𐏑 (npub1uwj…axfl) aqstr (npub1dsn…2h64) Turkey (npub1vkd…9g2t) 7f766a7dfd7ea23ffc24c7b27da138e8d81d1d0b3ca45c5da1a10e9d0778f5dc (npub10am…j8tf) OB (npub1u0g…tkzz) amethyst (npub142g…xrj0) craigraw (npub1hea…g9v2) Malos10 (npub17am…nldk) corndalorian (npub1lrn…qnw5) DuneMessias (npub1j6j…g7fw) M✨️ (npub1xy0…pf8a) ZapSparrow (npub1dgd…39f4) Rod (npub1r0d…fsft) 𓆩sᴇᴛᴛᴏ𓆪 (npub18ug…20ex) daniel (npub1aeh…4nwx) Moos (npub19qc…7xw2) Luxas (npub16jd…33sv) negrunch (npub1qqq…rfkq) Catrya (npub1cat…euhz) andreadcorreia (npub1zvy…vfj0) Fabian (npub1n0s…lahe) Anjhc (npub1f27…9swu) alp (npub175n…g6w0) roadstrapp (npub1cwf…5mmc) Freedom Tech Co. (npub1frd…h4dd) leo (npub1w9l…3tur) SnowCait (npub1s02…fxtw) shocknet_justin (npub1xvt…64sa) besoeasy (npub1hzn…l6zh)

I would like to meet @nprofile…a0td and @nprofile…4j2v in ...

2026-08-30T07:01:05Z

In reply to nevent1q…6ntf
_________________________

I would like to meet rabble (nprofile…a0td) and Evelin (nprofile…4j2v) in person. Everything is possible and can happen in this life. 🙂

A protocol in any case. Not another single centralized server or ...

2026-08-29T15:17:45Z

In reply to nevent1q…q2d3
_________________________

A protocol in any case. Not another single centralized server or service.

This made me realize that we need something like #Blossom but for ...

2026-08-29T12:51:09Z

This made me realize that we need something like #Blossom but for livestreams.

quoting
nevent1q…qzqt
Help get this on Nostr. It's genius but all the gated streaming sites take it down. https://x.com/rehan_shei/status/2093528415576211819

@nprofile…qagl I want to recommend you creating a PayPerQ ...

2026-08-29T10:27:26Z

PPQdotAI (nprofile…qagl) I want to recommend you creating a PayPerQ #Concord community. It's superior to DMs, especially for collecting bug reports from users, and it is like Discord but encrypted and decentral.

Best Concord client so far: https://armada.buzz

Concord specifications: https://github.com/concord-protocol/concord

Ok, I tried to DM you over Armada with both NIP-04 and NIP-17.

2026-08-28T23:08:30Z

In reply to nevent1q…7j7l
_________________________

Ok, I tried to DM you over Armada with both NIP-04 and NIP-17.

Can't DM you because you didn't set up DM Inbox relays.

2026-08-28T22:47:44Z

In reply to nevent1q…7j7l
_________________________

Can't DM you because you didn't set up DM Inbox relays.

Glass half full kinda day?

2026-08-28T10:29:05Z

In reply to nevent1q…a9wz
_________________________

Glass half full kinda day?

Glass half empty kinda day?

2026-08-28T10:28:38Z

In reply to nevent1q…wufa
_________________________

Glass half empty kinda day?

Nostr event nevent1qqsplaw20230rtdcpn3vq24y5k32rm4c92ml3mskr5xww0zvmg72hsspvemhxue69uhhyetvv9ujucn4d9kxg6twva6xsetwv45kw6rzda6hy6r0dajzummjvuhkummnw3er5un9d3shjtnzw45kcerfdenhg6r9dejkjemgvfhh2ungdahkgtn0wfnj7en00p68ymm5943kjurgv4ez6urjd9ek6q3q2rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43skreele

2026-08-28T08:18:36Z

anyone still here?

Maxbe it also was my tablet previously which was too slow. But ...

2026-08-28T00:33:06Z

In reply to nevent1q…h3g3
_________________________

Maxbe it also was my tablet previously which was too slow. But now I have the problem that the thinking Kimi K3 normally does doesn't happen anymore suddenly.

@nprofile…qagl Is it possible that Kimi K3vhas massive problems ...

2026-08-27T20:40:28Z

PPQdotAI (nprofile…qagl) Is it possible that Kimi K3vhas massive problems as of now?

We only have the new app on testflight now.

2026-08-27T16:01:11Z

In reply to nevent1q…46qv
_________________________

We only have the new app on testflight now.

I care so deeply for everything that I forget to care for myself ...

2026-08-27T06:29:33Z

I care so deeply for everything that I forget to care for myself and then, everything flips upside down 🥲 I'm okay, I just need a hug and a revolution.

🍺📖 Beerbook — a beer check-in app on Nostr. Built it ...

2026-08-26T23:16:09Z

🍺📖 Beerbook — a beer check-in app on Nostr. Built it because I've been using Untappd for 16 years and always wanted a Nostr version.

✨ Features:
• Beautiful picture-book page-turn reader (real fold animation, swipe or tap)
• Check in with photo, star rating, brewery + location
• Beer search: decentralized inventory + catalog.beer search
• Tag buddies on check-ins
• Web of trust feed filter
• Value-for-value ready with Zaps (untested)

Built it on a plane ✈️ with my OpenClaw agent.

⚠️ Beta — needs more testing and polish. Poke it, break it, tell me what you find.

🔗 Test it: https://beerbook-test.surge.sh
💻 Code: https://github.com/CentauriAgent/beerbook

@nprofile…qagl API keys don't load anymore on the API keys ...

2026-08-26T12:26:53Z

PPQdotAI (nprofile…qagl) API keys don't load anymore on the API keys page.

I'm more eager to drop Linux kernel in android and go to a ...

2026-08-26T06:52:54Z

In reply to nevent1q…jf67
_________________________

I'm more eager to drop Linux kernel in android and go to a graphene micro kernel.

@nprofile…99h6 @nprofile…htsr Can you please change music ...

2026-08-26T02:51:44Z

Fanfares (nprofile…99h6) arkinox (nprofile…htsr) Can you please change music event to kind 36787 as defined at https://nostrhub.io/naddr1qvzqqqrcvypzqx78pgq53vlnzmdr8l3u38eru0n3438lnxqz0mr39wg9e5j0dfq3qqxx6atnd93j6arjv93kkucv9awlv ?

Forgot screenshots for proof. ...

2026-08-25T19:07:16Z

In reply to nevent1q…j0tk
_________________________

Forgot screenshots for proof.

I added a Plebs tab to both main page and profile pages. Is this ...

2026-08-25T19:06:35Z

In reply to nevent1q…63kd
_________________________

I added a Plebs tab to both main page and profile pages. Is this what you wanted? The Plebs tab shows only videos with the #pv69420 hashtag, like plebs.app did.

I have added support for kind 1 notes with videos. Since there ...

2026-08-25T17:51:18Z

In reply to nevent1q…avlf
_________________________

I have added support for kind 1 notes with videos. Since there are so many kind 1 notes, I put them in a separate tab. You might need to refresh the page.

Ah, ok. It's a kind 1 event. VidStr uses video events as of ...

2026-08-25T16:22:55Z

In reply to nevent1q…x6ja
_________________________

Ah, ok. It's a kind 1 event. VidStr uses video events as of NIP-71, that are kinds 21, 22, 34235 and 34236.

Also you didn't submit this to enough relays. I needed to add more relays to see the event in my raw event explorer (https://raw-nostr-2.shakespeare.wtf)

Can you please link me one of your video events?

2026-08-25T16:12:49Z

In reply to nevent1q…uszv
_________________________

Can you please link me one of your video events?

They show up. plebs.app uploaded each video as regular, ...

2026-08-25T16:05:43Z

In reply to nevent1q…f0ct
_________________________

They show up. plebs.app uploaded each video as regular, addressable and kind 1.

I could vibecode one, but then you wouldn't see me as well. ...

2026-08-25T15:57:17Z

In reply to nevent1q…4dkk
_________________________

I could vibecode one, but then you wouldn't see me as well.

Is there any reason why you hate Lightning so much?

NEW #VidStr is now live. https://vidstr.shakespeare.wtf ...

2026-08-25T15:54:43Z

NEW #VidStr is now live.

https://vidstr.shakespeare.wtf

Completely rewritten from scratch with Kimi K3.

Old version is still available at https://47h1rs70oqaspur8bichfzalg0wnassb8d7tslfacl7hwyaxhkvidstr.nsite.lol

#ai #nostr #grownostr #marlowe #shakespeare

Derek Ross (nprofile…2szn) Alex Gleason (nprofile…g58a) Team Soapbox (nprofile…z2n3)