Blake
_@wako.ws
npub1ktw5...mrvj
#Bitcoin #Nostr #Freedom wss://relay.nostrgraph.net
Reminder: Twitter is blocked in Russia. This is one way to get access. https://github.com/xnaas/nitter-instances
May seem weird to be promoting the bird, however Nostr needs to remain censorship resistant to state based actors.
#[0] for nodeless.io, do you have documented webhook payload JSON? I can see the CRUD APIs, just not what the webhook should expect.
Does it return the same as the types GET _type_ Request for each?
I’ve just added a Dockerfile for nostcat, so you can run nostcat from a socket image instead of installing go and compiling. It’s only 30mb compiled.
Once a few more people can test it and it’s all good, I can maybe release a pre-compiled docker image.
GitHub
GitHub - blakejakopovic/nostcat: Websocket client for nostr relay scripting
Websocket client for nostr relay scripting. Contribute to blakejakopovic/nostcat development by creating an account on GitHub.
Anyone have a Nostr Tor onion address relay? I’m testing a PR to add support for nostcat.
If you’re not sure what WebLN is, below is a good primer.
My only next question is when will we get serious a web browser option that isn’t failzilla or gloatware? Safari extensions have issues too. These corporations are literally stonewalling alternative browser payment integrations where they don’t get a cut.
https://medium.com/@pavan.techie/making-bitcoin-transactions-smart-with-structured-metadata-1c3be0ab428
It’s also used by snort and Nostr web clients to support paying invoices and zapping.
GitHub
snort/packages/app/src/Wallet/WebLN.ts at 7a717a5c562c37806678844d24bc8bbf5d2af4c7 · v0l/snort
Feature packed nostr web UI. Contribute to v0l/snort development by creating an account on GitHub.
Updated my Nostr Event parser POC. Now extracts events, relays, bech-32 encoded nostr: entities.
If you want to get an idea of how much data a single fairly short event can parse into.. it’s worth a look. It’s kind of like an AST for Nostr events - that ideally can be used by rendering engines or whatever.
May look at adding #[0] ‘s NDK to optionally query pubkeys/events for more info.
GitHub
GitHub - blakejakopovic/nostr_event_parser: Proof of concept nostr typescript event parser to extract metadata, and aid in rendering html or general data processing.
Proof of concept nostr typescript event parser to extract metadata, and aid in rendering html or general data processing. - blakejakopovic/nostr_ev...
TLDR: they are making usernames/handles globally unique (previously case insensitive and appended with 4+ digit number). Display names can be anything. Usernames and handles only really used to connect or differentiate/compare profiles.
Effectively in a Nostr world, pubkeys are too hard to share, use a NIP-05 as handle, (Display) Name yourself whatever.
Maybe “Nostr Username” or “Nostr Handle” are a better lexicons for NIP05 identifiers. It helps take away the ‘verified/verification’ misunderstanding. I guess it’s possible to read-only login using your nip05 as a username too.
Evolving Usernames on Discord
Discord usernames are changing to remove four-digit discriminators. Display Names are being added so how you appear to other users stays the same. ...
#[0] my NostrGraph relay’s status in Damus has been flapping. Only started the last couple weeks or so. No changes my end, and server data seems fine.
Anything I should check? Maybe rate limiting or something is getting triggered.
Holy shit. This game nails the problem with moderation. Literally give it a go if you think moderation works. You’ll see how it’s near impossible to do quickly, it’s always biased, 70% accuracy gets applauded, you regularly make decisions (on behalf of everyone else) without any real way to know, decisions are highly contextual or location based - like legality, and so on.
And don’t forget moderators have KPIs today based on number of items reviewed.. they are literally paid more to think the exact same as each other and moderate with the same action (as many moderations are sent to multiple people to check consensus and that people are working and not blindly swiping/clicking).
View quoted note → 
Having been prototyping a Nostr payed lightning CDN, I’m circling back to read up on LSAT again.
Effectively it leverages the 402 Payment Required HTTP response, and a WWW-Authentication header (exactly my approach) and acts as a reverse proxy in front of a service. It doesn’t require private key auth, which seems great, but you also need to store state for a macaroon and a payment hash (which also allows sharing). LSAT does enable fine grain pay as you go payment models - perhaps interesting for Nostr services.
LSAT doesn’t seem to have really taken off since 2020. Maybe Nostr’s zap and lightning adoption could help growth. #[0] just released this LSAT demo as well, with split payments. https://weather-lightning.bumi17.repl.co
Anyway, I think it’s worth exploring more and understanding what options and approaches we have, that may be useful as part of Nostr functionality and economy.
LSAT: Authentication and Payments for the Lightning-Native Web
Today we’re excited to announce the release of our draft of a specification
for Lightning Service Authentication Tokens (LSAT). LSAT is
a new pro...
I’ve updated my rust Lightning webhook library example code for both BTCPay and LNbits - you literally can set some ENV vars, uncomment some code, and set your desired SQL payment code. Then you just create your invoices with metadata like a pubkey, enable web hooks, and you’re 😎.
GitHub
GitHub - blakejakopovic/lightning_rs_webhook: Rust library for handling BTCPay and LNBits payment and invoice webhooks
Rust library for handling BTCPay and LNBits payment and invoice webhooks - blakejakopovic/lightning_rs_webhook