Subnostr

you can turn this into a bot and publish 1984 kind, we relays or them clients can follow it!

It’s proof of concept, but I’ve added meta.spam_score to my event API. I still need to decide how to roll out the ML classifier at scale (it’s a bit slow atm without a GPU). I’ve only classified 40k events thus far to review.

I’m not sure publishing 1984 events is the best approach. Each spam message then would need another 1984 kind event. And just one spam message alone I have 360k+. But alas, it’s not too dissimilar to likes and how one post could have 10MM+ like events in the future.

https://api.nostrgraph.net/beta/events/note1da798nu47zk363rjddg37wlsgy0xw8y0w48yx0vrzfw6652tam3szpzre9.json?pretty=true

Or just stats

https://api.nostrgraph.net/beta/events/note1da798nu47zk363rjddg37wlsgy0xw8y0w48yx0vrzfw6652tam3szpzre9.json?pretty=true&stats_only=true

Reply to this note

Please Login to reply.

Discussion

someone 2y ago

or you could just tag the pubkey once and let everyone know it is a spam bot... then it is 1 event.

Blake 2y ago

Yeah, the issue is they often use a new pubkey per event.

someone 2y ago

Turning it into a bot will add transparency too. If a relay is saying I am following this bot then people will know that the relay is not a black box.

Blake 2y ago

I like the concept. The 1984 events could have a known pubkey that could be trusted by relays or others to label events as spam.

One issue is you would lose the spam score component. At what score would an event be created? Is that something clients should instead decide? The score could be inside a 1984 tag perhaps - but scores also could change or improve over time if an event was re-evaluated (perhaps a bug, or new data now correctly identifies something as spam).

someone 2y ago

Adding the score in the event is a great idea. If NIPs doesn't support, you can later edit the NIPs..

DZC 2y ago

If the event's recategorized maybe a new 1984 could replace the previous one?

someone 2y ago

This is awesome work!