Cool learning from this spammer: if the nostr client downloads and stores the spam event locally and the relay deletes later, the client doesnt get any notice it was deleted and must develop it's own ways to clear the local database out of it.
Same for local relays, like Citrine. Once it gets there, Citrine doesn't have a good way to remove it. The client will just be getting the spam event over and over again.
Thank you spammer!
The clients can help us, but this would be best resolved at the relay level né?
Everybody needs to do their part.
is a block/mute a subset of a reply, or is that a different kind altogether?
...just thinking that if blocking actually perpetuates it, then...it's almost like Greek fire
Yeah, anything that adds a ptag might perpetuate it. Reports, mute lists, etc.
The goal should be able to have better tools to clean up the local database as many of these events will get there no matter what.
how would the event get on citrine though? (besides being publicly available over TOR)
To me spam categorization and deletion are different events. Wouldn't exportable/importable spam lists make sense?
