We could just not use created time but arrival time/first seen.

Reply to this note

Please Login to reply.

Discussion

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.

Have poor rate limiting*

i see - mean every relay has do it in code level