/cc nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgkwaehxw309ajkgetw9ehx7um5wghxcctwvshsqgpjuxp8vd29p6ancknaztql3eajk52y8xkppfn7au7elkw9c68zg5hnqf7r

Reply to this note

Please Login to reply.

Discussion

This is how i do zaps. This is also why i have default zap 1000. It was never meant to be spammed like a reaction

Wouldnt an "OnlyZaps" mode feel rather quiet, then? Also intentional?

Whats wrong with quiet?

Nothing. I guess i disagree with op

Zaps as reactions are spam now?

Not everyone can afford to pay a dollar per like.

Its not up to me how people use zaps, i just have my opinion which is the minority

But yes zaps under some limit could be considered spam, like 1-2000 msats.

It’s like if you see someone on the street playing an instrument and you throw 1/8th of a penny in. Sure it all contributes to an aggregate but a zap is still going into their push notifications.

This is why we are planning zap notification limits sometime soon

Every zap matters šŸ¤™ they are high signal it’s not about an amount, it’s about the pow vs a simple emoji or ā€œlikeā€ reaction

I wonder if there’s a way for clients to better implement a minimum zap limit in the UX. šŸ¤”

Here’s what I mean:

LNURL-pay lets the recipient wallet set both a minimum and maximum amount for the payment.

If a user tries to pay less than the minimum, wallets like nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0s0pfy4z will immediately display the range on-screen. I tested this by using a Misty nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpzamhxue69uhkvun2daekstnwdaehgu339e3k7mgqyzt3r5dt4qr28g59lulg05t4jqkz7fg8gxrqm8r9jq7gkh5x867cz3f3ytq Lightning addresss, which has a 100 sat minimum to receive.

However, clients like Damus don't do this, and instead make an attempt to fetch an invoice, which eventually times out with an error message, leading the zapper to think the zapees’s wallet is broken, when the payment request is simply out of range.

If this information is shared between the wallet and the client, there could be some instant feedback returned to the user to let them know that the user they want to zap simply has a minimum, and they should zap a larger amount.

Oh yeah we could definitely incorporate this, not sure why we haven’t. It’s just metadata on the lnurl endpoint.

Let’s get that coded! šŸ”„

I wouldn’t say its a one line change though, there are a lot of design considerations nostr:npub1uapy44zhu5f0markfftt7m2z3gr2zwssq6h3lw8qlce0d5pjvhrs3q9pmv

For example, instead of just erroring on default nwc zaps it might make more sense to show a popup: ā€œdefault amount is less than minimum zap, do you want to bump up?ā€

Also i personally think minimum lnurl amounts are dumb. The minimum should just be there on the notification settings.

but even if they are dumb lots of people still have them, so we should support that instead of ignoring it

Minimum amounts are necessary for certain wallets. Nodeless Liquid-based Lightning wallets have a lower limit of between 21-100 sats, because it's really not economical to do less.

not really though, you can be annoying and spam 1msat every second

I'll allow it –> filou@walletofsatoshi.com

I think that’s the best way , to set zapping min 1.000 , but people can also setting how much they want to zap

On the setting .

Wallets that support zaps should offer notification settings for threshold amounts, as well as zaps without a message for example. It's a very simple feature to implement.

Here's an example from Kosmos account settings:

(I mean zap wallets *and Nostr clients*.)

Zaps are the perfect reaction šŸ¤™

Good Morning , friendsā˜€ļø