The right way to attack nostr is to outline the attack, release the code, give some time to prepare then carry it out in short controlled bursts
But it does need to be attacked and poked if we want it to actually work imo
The right way to defend the Nostr is to call the cops on the spammers
You actually think this way?
An attacker just wants to see nostr burn.
If it can’t withstand deliberate attack then it won’t last in its current form and we might as well learn where it breaks before building critical systems on it.
You are expecting every attacker to give you the blueprints on a silver platter. We were lucky with Emoji guy
Nostr has been getting spammed for years now and relays still haven't changed
I’m not expecting anything. I’m saying we learn from each attack and the more notice we get the better.
The situation @utxo the webmaster 🧑💻 describes is strictly better than a scenario where nobody ever telegraphs the attacks in advance. It’s a common practice in cybersecurity called “red teaming” and helpful if well intentioned people attack before malicious ones do.
Ok but relays have been around for a few years now and nothing changed except for the terrible WoT concept
There are paid relays and other filtered relays out there. WoT can work as long as you’re not trusting Reply-guy types.
We’re lucky that Nostr is an open protocol and anybody is welcome to build their own clients and relays on top to filter out the spam. It’s easy to criticize but most of the devs are building and running this infrastructure in their spare time for free so we should be thankful it works at all honestly.
When a builder thinks they're thinking like an attacker, but they're really just thinking like a tester 😏
nostr:nevent1qqsy99jgk79nsjuaf0r55k6rth3v25krrl4wvq6hxusr9ws84mp52fgpz4mhxue69uhkummnw3ezummcw3ezuer9wchsyg8zenmu7gzq8ulj5jj4kv50ph3muwz43f747vmr9ld2alrjdswgavpsgqqqqqqsgg7yvj
nostr:nevent1qqsy99jgk79nsjuaf0r55k6rth3v25krrl4wvq6hxusr9ws84mp52fgpz4mhxue69uhkummnw3ezummcw3ezuer9wchsyg8zenmu7gzq8ulj5jj4kv50ph3muwz43f747vmr9ld2alrjdswgavpsgqqqqqqsgg7yvj