So, thinking about this technically:
If I as a user want to participate in this, I follow a particular npub that is designated as a feed value threshold. Let’s say I follow @Add4Ads100 or @Add4Ads50 depending on my desired sats threshold. Not sure if the open wild is the best place to try to pull it off. Client side implementation would help if a NIP was drafted. I set my Add4Ad settings that as a user and the client shows the ad, which zaps me 90% or 100% of the sats for me to see the ads. Since fees are unreliable to get that to me the client can make sure that it’s seen giving me a dismiss by showing it to me more than once to make sure that I got it. Advertiser won’t want to just shoot their zaps into an abyss. The advertiser submits their post with the inclusion of @Add4Ads50 with that listener generating an invoice DM to the advertiser with an open budget amount, and once the desired budget is paid the profile runs the ad for any of its followers that have settings fitting to the display criteria to see, interact with, and receive zaps from accordingly. The interaction is what triggers the zap. If they don’t interact with it, like it or dismiss it.. no zap. Seems like there would be an entire span. Engine spun up to try to gobble up as many of these apps as possible that are not real people. Would have to battle that. On the side, there’s an opportunity to let users configure the type of ad content filtration and zap levels. It could eventually get creative with the client side zap levels per content type. As a user, I don’t mind advertising. But I do want to choose it. And no, I don’t want you to choose it based on it, psychological or biological profile that you have of being in a database. This brings it into the client settings of the nostr user. Is there any meat on the bone for this approach to the idea? What’s missing? This kind of thing is also where my NIP-G0 could help, as profiles and content could be aligned at various levels of geocoding the events and npubs. This reply is abrain dump. But just seeing what sticks.
Login to reply
Replies (1)
*spam engine …not “span. Engine”