There’s a friction point between the zap/V4V/donate approach and the paywall/shop/set price approach.
I think there’s UX to learn from prior art like games with content you unlock, without your base experience detracting much. Keep in mind global will be cut up into views soon, and the firehouse will always be Wild West content. Most people wouldn’t ever see that paywall unless they follow that account.
There is also a difference between a timeline feed and what is effectively an advertising feed - as paywall previews are basically advertising. Occasional promotional messages of paid content is typically fine - especially from people or producers you like.
It’s always tough asking for money before you know what you’re really buying or before you can evaluate value for money for you. Is the article just waffle clickbate? Did I learn anything or was it just AI regen? Images/media can be easier to describe pre-payment.
Paid.
lightning:lntbs150n1pjxj3e7dqqpp55f7en68mcxq5tlvaxxxj5fa2vpdnqg9endtns0jqzm463velqvsssp5wj3ap38hu7efpc4lah8cx4usnpakn8fs2nknk9lmjyk7c5h9u37s9qrsgqcqpjnp4qwuff7zmlxrjjr2xj3uj2aghvm7j5sg3gcw52m94rvw83fpkv64egxqrrssrzjqftf3ny6cc3lt5d67433puh3kcklllhy8l7dktpqej65racyjl25qqqqqqqqqqqqqyqqqqqqqqqqqqqqrcru9hhnw5cg066jupwjpkssh4lfquvpzq8t3rxd6tg640hy399w2jwagk3cg7av84xx5ahfer79whvxjyg4ax5r4d9kr36pjqfg9jp7gqa2ppa3
Halt! This is a random citizen credential check. Please provide your proof of government worship.
If enough people care they’ll recreate, rebroadcast, or start their own relay.
For sure. I think there is a cross-over for custom views, and possible add mute rules to a specific view. A view could include one or many lists - and perhaps media type selection.
By organising are you thinking about views, or local virtual folders, or something else.
One of my main concerns atm is new users starting with few relays, no following suggestions, and ending up in global - which is a bit of the Wild West - as it should be; but with filters.
If API key can be replaced with a pubkey + NIP-98, then this approach can work, and provide possible payment options.
The image was a POC for paid services manager built into Damus.
https://gist.github.com/blakejakopovic/fe384b8fd97231ece267bf264eb466ef 
POC Damus Mute Filters. These are locally run filters that you can fully control. 
Here’s a early draft of a possible way we can define Nostr services in a common way. It has a lot of gaps, however I'd like to start by gather use-cases we want to support.
Ideally other services can include premium relays, CDNs, trending APIs, POW, etc.
Early feedback welcome. Can create a formal PR/Issue for this, so we can collaborate more easily.
CC
#[0]
#[1]
#[2]
#[3]
#[4]
https://gist.github.com/blakejakopovic/eb82a2e417fd0846f2afcfc380988520
Maybe we end up with some openapi (swagger) style definition. May be reinventing the wheel - or perhaps greenfield makes sense.
Happy to try support any APIs.. I’m not trying to solve any direct problem I have - just noticed that most Damus services can be extracted out into API definitions that could be reused and shared (translation and upload) across apps.
And if we have a service offers concept, we can look at optionally supporting paid services and making it as easy as possible to start or swap.
Maybe this could help. I’d like to try model NIP-05 as a service type.
https://gist.github.com/blakejakopovic/eb82a2e417fd0846f2afcfc380988520
Here’s a early draft of a possible way we can define Nostr services in a common way. It has a lot of gaps, however I'd like to start by gather use-cases we want to support.
Ideally other services can include premium relays, CDNs, trending APIs, POW, etc.
Early feedback welcome. Can create a formal PR/Issue for this, so we can collaborate more easily.
CC
#[0]
#[1]
#[2]
#[3]
#[4]
https://gist.github.com/blakejakopovic/eb82a2e417fd0846f2afcfc380988520
Hot off the press, this one is kind of related, but focused on the HTTP Auth flow.
https://gist.github.com/blakejakopovic/fe384b8fd97231ece267bf264eb466ef
Here’s a early draft of a possible way we can define Nostr services in a common way. It has a lot of gaps, however I'd like to start by gather use-cases we want to support.
Ideally other services can include premium relays, CDNs, trending APIs, POW, etc.
Early feedback welcome. Can create a formal PR/Issue for this, so we can collaborate more easily.
CC
#[0]
#[1]
#[2]
#[3]
#[4]
https://gist.github.com/blakejakopovic/eb82a2e417fd0846f2afcfc380988520
Perhaps. Maybe you just train your models better. People can really only do so many disturbing things.
Using a rare, marginal, and extreme use case as an argument for a mass action is no different to the principle behind KYC or internet nanny filters without Id. It’s why we have so many edge case stupid laws that are applied way beyond their initial implied scope.
You will never be 100% safe if you ingest information that isn’t pre-moderated. Nor with moderation either.
Or something as simple as this.
Ordinals are calling… 1️⃣2️⃣3️⃣🔥
The real #zap generator nostr:note18xlvpv5xvjtw5v6vatlh08qzwt75yv9t0mm99794932pdmyngzjsaa6763