Oddbean

This could be waaaay worse. I need a way to opt out, set a minimal zap requirement, etc. Does muting work on zaps? We’d need a whitelist for zaps - but then that really limits the potential for zaps. Advertisers are ruthless. They’ll create accounts, zap, and abandon them all to your doorstep faster than you can blink - there is nothing to stop them. They can zap you 1 sat, and it’s a home run in terms of conversions. They’ll play this game until the number of sats they need to send is no longer profitable - and that should be our primary way to control our experience with advertisers.

100%. But then you’re limited in your choice of clients. If you decide to try out another client, you could be inundated. Worse, this could be used for griefing in the worst kind of way. In short, the network could easily be used against you by those who could pay. And creating a new npub is just relief from targeted griefing. The ad bots wont be slowed. Signal will be lost. Nah, this needs to be some kind of opt-in feature at the protocol level. Send a zap? Fine. Add some text? Maybe… Bundling media with it? Starts to become problematic. Maybe this needs to be a relay-level of control rather than protocol. I’ll gladly run my own version of a relay that says “ you can zap me, but each additional byte of data accompanying the zap requires X more sats to make it through”, where I can configure X.

Agreed. If there are enough people complaining, which I'm pretty sure there'll be, then there'll be a NIP about it and client/relay will implement the NIP. Advertising will be a cat and mouse game where NIPs will need to constantly evolve to protect users.