Being transparent is critical. Nostr has faults today, and we can build greater protections over time. It’s important to call out areas that need work - or assumptions that’s aren’t what they may appear. Censorship resistance doesn’t exactly align with privacy. View quoted note →

How much interest is there in a open-source universal rust webhook library/server for BTCPay and LNbits? I’ve written the BTCPay version and it’s basic, but functional. And I’ve looked into adding LNbits, and it’s just a single webhook payload and easy to add support for - but a bit of extra effort. Anyway, let me know if LNbits support is of interest and I’ll make it universal instead.

Verifying my Nostr Nests identity: ndd1GrC2BnKhHH7-9iJOCM7BWr7HtEECcvKeTyH7RUs

Nostr Nests

Join this audio Space

Another nice open source Nostr Event signing and Delegation web app, nice for tinkering - authored by #[0]

NostrTool

https://HTLC.me is an awesome testnet Lightning wallet for playing with test invoices.

I’ve written two basic example rust projects that I’ll try open source this week. 1. BTCPay server webhook that can update a database on invoice payment. 2. Nostr 402 Payment Required paywall server that uses NIP-98 HTTP Auth after payment to authorise access. It likely can generate lightning invoices before payment too. The basic idea is that if you ZAP or pay an invoice, the same URL can return the desired content if you sign a Nostr message that proves your private key which can be used to check prior payment. Ideally we can support some kind of Nostr client app UX, where content can refresh post-payment.

#[0]​ what would be really cool is a way to optionally auto-refresh an event’s embedded media after a zap has been paid - maybe with a minimum sat. Would be nice to use the same URL, that returns 402s without payment, and likely a blurhash, but 200s after zap. Maybe the post-payment requests includes a NIP 98 header for auth. Main risk is privacy around sending your pubkey for all media requests because you don’t know if you’ve already paid (before first http request) - and that’s a privacy/tracking vector. Ideally private zaps could unlock content too.

GitHub

nips/98.md at af4cbfbddb2900b7bc4a56b57430989e8b613006 · nostr-protocol/nips

Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.

For maximum censorship resistance, you want to be a fish in a school of fish - very hard to isolate and eat. Adding fine-grained (often ‘controversial’) metadata to single you out, makes you, and those who interact a target.