they'll just adjust the timestamp to circumvent this..
nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe could we have a setting to reject all replies to a post that come up less than 5 seconds after a post? Humans can’t reply that fast
Discussion
will it not stress CPU?
We could just not use created time but arrival time/first seen.
good thinking
npub creation or first post timestamp can used as FILTER KEY
no legit manual npub or test npub can still be allowed
any npub age of few secs or hours can be blocked / dynamic cache block-listed for spamming
if they bypass using mass old npubs? then throttle can take care from there
💯This too!
First time this npub is ever seen replying immediately to a post? Bye bye bye script kiddie spam
First time in a long time this npub is ever seen replying immediately to a post? To the dumpster it goes. This prevents pre-creating profiles that then can be used en masse
correct approach for NOSTREAM
others should mirror their code once u do
- time gap between reply
- age of npub
- frequency of reply or new on the SAME relay
(no human can do this within secs - even telegram discord have this control )
then final hammer WoT or POW is always there now MOST relay software
NIP-42 , PoW, WoT are like bazooka to stop all new npubs legit + rouge
The problem is that addressing it at the relay level won’t work because the spammer is sending brand new npubs and different messages to a bunch of relays. Nostream already blocks a single IP from sending too many messages in a short time but let’s be real most relays aren’t Nostream and poor rate limiting.