Subnostr

The problem: when a brand new pubkey starts sending events, it can be difficult to tell immediately whether they are a legitimate user or spam.

Our solution: accept all new user notes temporarily in a separate database. As they send events, we continually evaluate their behavior based on several rules (and eventually by a trained model) and approve/block the pubkey.

If approved, all of their old events get added to our aggregator relay and the user is immediately discoverable. Their future notes will also go directly to the relay. If blocked, the events are sent to a purged database (for transparency and evaluation) and never reach our relay.

Still an early WIP but coming along! It doesn’t solve all the issues but it is a massive improvement on our current rules. nostr:note19kp6d4lmdjr8r0hn0uyx62jdreu5xcyxz7zm2pxwsrd6hcferdtqyx6nxp

someone 1y ago

good idea. are you doing this in write policy or strfry c++ coding?

i was thinking of something similar with write policy but then Doug said async acceptance of notes is not possible.

Reply to this note

Please Login to reply.

Discussion

Mazin 1y ago

We are using a write policy to send the notes to a separate application/db that handles the “purgatory” state. Then that application inserts events back to the relay as needed.

Would not be able to do it all within a write plugin.

someone 1y ago

so you first reject the notes. then accept in the second processing.

Mazin 1y ago

Yes, but the initial write plugin checks if that user was previously approved and if so auto accepts the note. So only “unknown” pubkey events are sent for secondary processing.