#nostr #蹃驼
quoting#Nostr I think I'll be tinkering around with some more strict rate limiting measures in #Nosflare relay that stores the hash of the content of each note's json. In a similar way I have it check for duplicates already on #Anonostr but this would apply relay wide.
note1p4v…c53k
This way bursts of spam notes that repeat the same thing, regardless if disposable npubs are used, can be stopped quickly at the relay level. And it would be quick to adapt if the spammer adapts. Of course, will have a filtering logic available for any single word or phrases you'd want still allowed. But might be useful to block X thing once repeated Y times within a given time frame.
I'm fully aware that a spammer could iterate through each note with completely unique content to bypass. And that's why I'm thinking the next best feature might be to have a minimum created_at requirement to publish to the relay. When an EVENT message is received it goes into a queue and the author's pubkey is checked against another relay for its oldest created_at event. If it is less than X time old, it gets dropped.
Could be something relay implementations collab on to help the community. Some standard that let's relays share this data and make it easily REQable. Thoughts? #AskNostr