Lots of cool things going on with Nostr but still no one is doing zap-gqted DMs.
let me set a threshold to be able to DM me, and give me an allow list for users that I trust that can DM without a zap.
nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzpmhxue69uhkummnw3ezumt0d5hszythwden5te0dehhxarj9emkjmn99ue6qm68 nostr:nprofile1qqswum4p82uluhz2dr40nvdrflspffntgqghc58w9fs57nx6jkdkuaqpvemhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0dec82c33v9jksvn6wu6x2mr9waun2d3cxfk8scek0phxcut6dfh8s6mnwyenqvm8wa6nymnsveshsep589mx6er9xeckxuf5demhs0mzwfhkzerrv9ehg0t5wf6k2qguwaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skchplh66 nostr:nprofile1qqsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygpp4mhxue69uhkummn9ekx7mqppamhxue69uhkummnw3ezumt0d5m255n8 you guys are all doing cool things, how about it?
Replies (3)
Very much not my area of expertise, and something I don’t think would get much use. Paywalling inbound messages is extremely hard to pull off. I can’t think of many successful example. LinkedIn charges for a premium level to use InMail, but even they don’t have per-message rates. Lightning would work well for this in theory, but in practice it’s hard to say.
I think relays could set sat required policies for broadcasting certain kinds. So is possible but onpy as far as you interact with relays with the policy. I dont think thats feasible for an npub to require that policy, just not how nostr works from my understanding.
It might work with a new NIP that only displayed the contents (or even existence) of a DM if a successful zap were attached to it, but of course, it would not be backward-compatible. That’s as far as I can go with this idea right now.
