I haven't had spam problems since the big spam era back a few months ago. Clients have at least these options:

1) banning pubkeys -- if a pubkey becomes a spammer, ban it

2) rejecting new pubkeys -- reject events from pubkeys you have never seen before

3) require a social connection -- block replies from people with no connections in your social graph

4) make the relays do the work -- block replies from relays that aren't known to be good spam filterers

5) block by content -- use some email-like bayesian spam filtering that bases it's decision on the content

6) require pow -- on the message, or on the pubkey

Relays can also use IP address reputation, requiring payment, or just human eyes and decision making.

Reply to this note

Please Login to reply.

Discussion

I head from a brazilian bank VP, some weeks ago, that his bank:

- suffers 100M connections/day suspected of fraud

- between URLs, social media accounts, and emails, they ask to ban 700 URL/accounts/emails per day due to fraud, often phishing and impersonation.

the scale is overwhelming. so much that I actually believe X/Twitter that when the followers count decreases, it may be robot prunning and not censorship (at least sometimes ;-P )

Nostr would have to grow much before attracting the same kind of interest, but imagine hundreds and hundreds of replyguys, everyday. How would be the process to deal with hundreds of such requests each day, and that from one bank?

2, 3, 5, 6, 7 and 8.

I also haven't had spam issues (while it was happening). However, I only limited my relays to paid and web-of-trust in a client that doesn't yet support retrieving from NIP-65 listed relays and etc. This however created a centralization problem with notes from many different authors coming in from the same relay, and also the possibility of missing some valuable notes. This is one of the reasons why I started having my relay sync notes for my contacts from their listed relays, to not have that centralization. Lots more to do here. Using an LLM to filter comments by relevancy, ecash/lightning for DM requests, better crawling of referenced notes and etc.

I thought private community relays would address the problem as well.

Most client's suck at swapping out relays tho. That's mainly why I don't fart with relays.

yeah i agree on the swapping out part is an issue

ok how about accounts that get flagged by other users and if they are continuously flagged, it will cost them more to post to the network?