Nostr Compass Podcast #39
from Towards Liberty Podcast Hosted by Max
Max covers signed Git workflows, browser publishing, Nostr client updates, protocol implementation, and how URI links and event references work. Guests: nostr:npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vt Newsletter 39 · Nostr Compass Android source 0:00 Signed git workflows move CI, private repositories, and releases onto Nostr Max opens this edition’s nine recordings with the ngit v3 launch and its signed Git workflow over Nostr. ngit-grasp v3 adds private repositories through GRASP-08, while ngit-ci 0.1 carries CI instructions and results as signed Nostr events. Max discusses working privately before a public release and considers sharing spare CI capacity. 3:13 nsite-clay makes browser publishing recoverable An August 31 signer-prompt fix, publication recovery, and September 2 editing controls make nsite-clay a browser publishing tool for a single-page site. A user edits the document object model in place, serializes the result, uploads it as a content-addressed Blossom blob, and republishes the site's NIP-5A manifest. No local build or server is required. 4:53 NIP-A3 payment targets reach three clients From September 1–3, Amethyst, Grimoire, and Pollerama implemented NIP-A3 kind 10133 payment targets. Amethyst offers an opt-in handoff only when a compatible target exists and does not turn it into a zap; Grimoire uses a fixed registry before building wallet URIs; Pollerama validates Monero addresses and fetches the author's relay list before querying targets. Each client still needs an allowed payment method, a relay route, and an accurate display. 5:16 Ditto expands Blossom fallback and mirroring Max explains how Ditto tries fallback Blossom servers when the preferred server is unavailable. He also discusses mirroring uploaded blobs so media can remain available through other servers. 5:46 Nostr Implementation Possibilities NIP-01 clarifies limit: 0 as a live-only subscription: no stored events, an EOSE message, and continued delivery of matching new events. NIP-78 recommends NIP-42 authentication and author-only access for app data kinds 78 and 30078; this is not a confidentiality guarantee. The open NIP-AC proposal uses ephemeral WebRTC signaling events and kind 30600 discovery. 8:08 NIP Deep Dive: URI Links and References in Event Text A Nostr identifier needs a transportable meaning before another application can open it. NIP-21 puts a NIP-19 identifier after the nostr: URI scheme, giving browsers, operating systems, and applications one dispatchable form. NIP-27 defines what that same URI means inside readable event content. 8:28 URI dispatch and NIP-19 semantics NIP-21's grammar is nostr: followed by one NIP-19 bech32 entity. nsec is excluded because it encodes a private key. There is no authority, path, or query component, so a conforming link is nostr:npub1..., not nostr://npub1.... A platform or client may register as the handler; the specification does not choose the installed application or define a web fallback. 10:35 NIP-27 rendering and optional tags NIP-27 uses nostr: URIs in readable event content so clients can render profile or event references. Max explains how a mention picker writes those URIs into signed content and how other clients display them. Optional p, e and q tags support indexing and relationships alongside the reference; displaying a mention alone does not require a notification. 12:19 Trust, failure behavior, and client implementations note and nevent refer to immutable event ids, while naddr resolves an address whose event contents can change. Max discusses client choices for previews, profile metadata and URI handlers. He closes by thanking builders and inviting listeners to contribute through the Nostr Compass Logbook. Originally published by [Nostr Compass](https://nostrcompass.org/)
Embed this episode
Chapters
- 0:00 Signed git workflows move CI, private repositories, and releases onto Nostr
- 3:13 nsite-clay makes browser publishing recoverable
- 4:53 NIP-A3 payment targets reach three clients
- 5:16 Ditto expands Blossom fallback and mirroring
- 5:46 Nostr Implementation Possibilities
- 8:08 NIP Deep Dive: URI Links and References in Event Text
- 8:28 URI dispatch and NIP-19 semantics
- 10:35 NIP-27 rendering and optional tags
- 12:19 Trust, failure behavior, and client implementations
No transcript yet.