There are plenty of better ways to raise awareness, start a discussion, and make Nostr more resilient.
This just causes unnecessary confusion for users and fire drills for other developers.
nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj , you do you, but this sort of thing is disappointing and childish imo.
I agree, Jeff. I always prefer to disclose these types of issues and vulnerabilities privately. That said, Semi's actions let the cat out of the bag and people have already started using it prior to me sharing his note. I wanted to let people know what's going on.
I believe you hat Primal will have all of this fixed in the near future with custom user controls. I'm excited to see what they produce as I think Primal is a great client and is doing great things for Nostr.
I wouldn’t even call this a vulnerability. It’s just a partially finished (known to be naive implementation).
We’re not doing ourselves favors by expecting fully mature software at this stage.
I appreciate the poking and the experimentation but the way it’s done just feels likes it’s in bad faith rather than collaborative or helpful.
