good zap zap all!😀
Somebody want zap me?
You zap me, I kiss you.
On the sea of souls, please, Remember of me.
Please! Zap me dad! Please! #zapme
zapme, please! 😀
zap me, please.
zap me, please.
zap me, please.
Zap me your credit number!
Zap me with all your energy!
I want feel all your love!
I don't think you see what I see. this protocol as is today is dangerous to end user because client/relays/app have too much power. Should be compatible with web5 where my data is mine. I should send at relay who I am and what I want share with world. in this protocol not. I found a bug very dangerous to end users. I am not joking. If I lose follower is not problem at all, if is lose my configuration of my website or other input I set on a client is not a problem at all, but if my customers pay in lighting and I lose my sats because a client change my lighting url is a problem I lost money and I need to send to customers my service/product for free because him sent money but not at my address, at address who nostr client changed maybe not for because an owners bad behaviour but maybe the nostr client was hacked. my english isn't good, but what I found is very dangerous to me. Nobody as answer me for now. I hope tomorrow someone contact me about that.
I see an important security bug by design in nostr protocol. need to fix asap. Can you contact me? Thanks.
maybe I should talk with @fiatjaf? I don't know if him know what I see, but for sure I see a very bugged protocol about security here.. For me that is more important than UI bug fix like this one of today https://github.com/fiatjaf/bisu/issues/1
Guys, after 3 days here, I understand that: this protocol is dangerous by design, need urgently update. Please, send this message to the devs here so we can speak about it. #plebchain
Guys, after 3 days here, I understand that: this protocol is dangerous by design, need urgently update. Please, send this message to the devs here so we can speak about it. @plebchain
