Pointed out this inherent issue with how #Nostr currently works, in a couple of previous notes & replies.

The bigger #Nostr gets, the more will this kind of spam become everyday business. #Nostr needs way stronger spam protection!

nostr:nevent1qqsw7smhm6p3l78evt0u9pmkkv7yjup779cps7qaa0r2a9t9uex2pmspp4mhxue69uhkummn9ekx7mqzyrak0epg7tg0z54r0vjagj65gungu77lnsfzpfjsptyvtc7hr9zz7qcyqqqqqqgf5n5kg

#Spam #Scam #Phishing #SpamProtection #Consumerism #ConsumerProtection #Exploit #Vulnerability #SecurityVulnerability #NostrClient #NostrDev #DevNostr #Dev #SecOps #Fake #FakeAccount

Reply to this note

Please Login to reply.

Discussion

Hmmm. Interesting. Suspected it was a directed attack.

Thanks for the reply.

Literally months ago, Somebody already doing the exact same similiar spam as what this user did:

npub1x0rg2evrkhx4jv49kvumsufc52mtwhur3pshvqezsnfnnncs2nashxcerr

Literally has giving warning about this spam multiple times, But Nostr developers just seems taking it easy like a cake or even solving it seriously at all.