Thinking out loud how we can easily support Nostr 402 (payment required) and 401 (unauthorised). Good news — I think we can just use a WWW-Authenticate header to indicate supported auth methods - which can double as a way to prove payment.
Basically, for 402 Payment Required, we can return a mime/type suitable response.
For an image we can return a blurred/masked image and maybe some kind of indicator it’s paywalled with two HTTP headers. An invoice header to optionally pay and a WWW-Authenticate with something like Nostr-NIP-98.
Doesn’t solve the issue of knowing if you’ve already paid. If you get 402, do you automatically try auth to see? Privacy issues exist. Do you try auth once before invoice payment as a sense check? Also doesn’t solve normal web browser inter-op. Maybe closer to an approach.. but lots to solve still.
One possible approach is to whitelist domains you are happy sending HTTP AUTH events for accessing the content - paid or private.
Blake
_@wako.ws
npub1ktw5...mrvj
#Bitcoin #Nostr #Freedom wss://relay.nostrgraph.net
Sometimes it seems like ideas are common sense - however the majority that get adopted are hard fought.
An example with BTCPay server resistance adopting LNURL. Not trying to call people out.. this happens behind most innovation - however it can make us appreciate those who keep iterating and striving for better. Thanks 😊


I haven’t read the NIP for implementation details, however this is a much nicer way to support moderated and curated content for Nostr. Opt-in, easy to follow competing/alternative methods (humans, AI, statistics, topic enthusiast, etc), it focuses on its own content and not hiding/suppressing other content, can be primarily hosted by specific private or community relays, etc. and when we get local client keyword/hashtag filtering, you can personalise it even more.
You can build a custom feed admin view that makes it easy to repost existing Nostr events or post new ones. You could even accept proposals for content to get added. You can have multiple curators or just one. You can enforce rules, like required hashtags or content warning on every post. You can suggest accounts to follow or click to follow all when someone joins your community - perhaps similar to discord chat channels - but post focused. View quoted note →
I was going to give my Bluesky invite away for free without using it. Sadly, I’m not sure I can morally object someone to such a scam-social company now… View quoted note →
I’m tired of chatGPT’s apologies.. and the endless overconfidence. Did they ask it to behave like the little boy who cried wolf?
It’s basically just a fancy auto-completion at this point.
How take-down resistant do we think domain names are?
I’m experimenting with a Nostr service that can allow you to use your own custom domain. Benefits include your Nostr events referencing a domain you control, so images or content references don’t break if you change to a new provider - or if you decide to self host.
It can also be an auth proxy to validate access or membership to that content.
Invoices can be wrapped for privacy and be atomic - so the provider and the creator get paid at the same time.
I like the Nostr torrent media idea, however content behind private membership or a paywall doesn’t really fit that approach.
GM buidl town ☀️ 🫖
Under a ‘Moderated’ Nostr would this be flagged/labelled “Political Protest”? Would you even see this? Or only what people in power want you to see?
Seems like fair concerns from the people?
"Another thing is that they are making us suffer economically, energy is too expensive and so is food," she said.
Protesters at the "Czechia Against Poverty" rally called by the small non-parliamentary PRO party also slammed Fiala's cabinet for soaring public deficits and for poor communication with voters. View quoted note →
#[0] have you seen this? 
GitHub
GitHub - lnbits/scrub
Contribute to lnbits/scrub development by creating an account on GitHub.
Just pushed a PR for lnproxy that enables support for a service provider to add a fee to an atomic invoice where both the service provider and a content creator can get paid upon successful payment/settlement.
Effectively this is like a split payment, where the service provider can add a dynamic fee on top of a seller price, that can cover hosting, or whatever costs the service provider has.
https://github.com/lnproxy/lnproxy/pull/24
#zap per second


Past hour

