I’m still working on Nostr spam detection and prevention - and ways the network can communicate and filter it out.

Been focused on event processing as the network has now 100x since I last focused on scaling. That’s almost happy - so I can focus on more innovating stuff.

Thoughts on perhaps a wss://spam.NostrGraph.net relay that only broadcasts 1984 events with a tag of spam_score (where the score is likely > 90%). It does mean each spam message triggers a 1984 message (or perhaps batched) - and this could be 1000s events/minute or more in future.

I drop spam now and don’t persist those events, so having a meta.spam_score on my API or relay published events to websockets is likely ok - but again perhaps not ideal.

I’m leading toward the approach of a relay service that can reject events. Similar to the authentication that checks if a pubkey has paid, it could be used to check if spam score is greater than a per relay threshold. Issue then is each relay needs this service with a model and the model needs to learn - or it will miss new spam formats.

Thoughts?