Bitcoin and Nostr are two different protocols and networks (though undeniably complementary) because money and information are different beasts.
They could compliment each other (and I honestly think they do it very much), but they both exists on their own.
Nobody is saying information has no value, don't try derailing the conversation, please.
🫂
Replies (16)
I am not trying to derail. And I agree that they are complementary to each other. But I also know you cannot separate them from each other.
The point of a zap is to link your social and financial information in a single pubkey.
You don't get to "separate" two different things.
Many Bitcoin users don't even know Nostr exists, and a lot Notr users don't use Bitcoin.
Zap (linking social and financial) was meant to be opt-in.
But you've made it on by default and not even able to opt-out.
But you already know that. The problem is that you consider it a feature, when it actually isn't.
It's not a feature in my mind.. it's just not an opt-in process at all. Youd socially linked transactions will always be public as long as you send them through any Nostr client. Lightning, no lightning, it doesn't matter.
The only way to opt out is to have a Bitcoin wallet that no client sees. And never link the two. You can opt to not use the zap features on a Nostr client but all off those features are there and those wallets are all public.
The recommendation I make to anyone is to have two separate wallet groups. Public and private ones, regardless of the tech stack. Never put your private lightning or cashu wallet on Nostr. Similarly. Never mix your Nostr on-chain wallet with your private on-chain wallet. Never transact between any of them. If you do it once, your private setup is already exposed.
Again, it's not what I chose to use. It's about signaling others my preference, if they decide to interact/zap with me.
Like I am trying to say, we can code your preference... But historically every client just ignores it.
Sorry, but that's not what you are doing.
Showing upfront the zap-onchain option to every user, what you are actually doing is pushing the users into the dangerous path of mixing their "nostr public wallet" and their "private onchain wallet".
You are not helping the user, not at all.
🫂
Maybe I am not making myself clear, we can add this, but seeing how every company in our space just adds bullshit to pretend that things are solved when they are not.... I don't want to participate in that disinformation campaign...
Your client could start by taking it into consideration, if you think it could be a good idea.
But we have lots of warning messages when putting money in and removing from it. As long as they receive in Nostr and send in Nostr, everything is fine.
The disinformation campaign is showing onchain option to every user, knowing that most of them using other clients will never know about this option.
Just my opinion, ofc.
I mean, if we had to remove features that we have but other clients don't see it, we would only have one feed and nothing else.
The funny part is that I had the exact same discussion when doing pronouns in people's profiles and some users wanted me to hide it...
Actually, I have this discussion in virtually every feature we add. There is always somebody asking me to hide things without understanding that it doesn't change anybody else's view of you.
The best place to put those warnings would be in the opt-in option, imho.
That would be the best option to protect the user into a possible future privacy leak.
Again, as I said, you think this is a feature, but it's not if it's not opt-in.
It will never be opt in. It doesn't matter what we do. Hiding it doesn't make it opt in. In this case, nothing ever will.
