Yeah, this is on Amethyst

Reply to this note

Please Login to reply.

Discussion

Oh lol my bad

#[7] zaps toggle please?

There we go

The proper solution is that you should disable zaps on your lnaddress if you don't want this as public info

Sorry bro, disagree. Proper solution is to support zaps independently of LN Adress.

So you can both receive sats privately + as zaps, dependning on who wishes to send where.

Disabling zaps doesn't stop you from receiving sats

No, but puts the onus on receiver

Whereas "zaps toggle" sounds like sender feature

Yes damus will do this, but it doesn't stop the sender from sending zaps when the receiver doesn't want that

True, thats a separate feature.

Could be part of config on advanced receivers nodes

"if amount > X, dont emit note"

"if sender is a follow, always emit note"

etc

For sure

This is public info. Do you really want a toggle if everybody else can still see it? As long as you accept zaps, this will be the case. All relays have this list, all clients have it too. Making it invisible on Amethyst won't solve the problem.

Maybe damus can make it so that it sends a signal to wallets that it doesn’t want to know information about payments #[5] ?

clients will be able to make anonymous zaps but it will still show the amount in the zap note. Users who don't want public zaps should set allowsNostr to false on their lnurl-payrequest endpoint or remove it entirely