Wot cuts out new people with no recourse for them to be discovered. Filtering non-nip5 verified profiles is a better solution.
Discussion
New people could ping someone they know out of bound, or use ecash.
Nip5 can also be used if you have (web of) trusted domains, especially when something like Ditto takes off.
Client side muting still allows people to peak into their replies and repost/zap someone into their web of trust.
Different clients and relays can try a combination of things.
nostr:note1cjq2ucwkh83x43juvu7fs0nn5lwjz6a4vasxwz4478v04ql85f4s5dvhj9
* out of band
nip05 is not verification, its utterly trivial for spammers to have a nip05
They are going to purchase a new domain for each bot?
Nip-5 providers would be incentivised not to let spamers use them less there whole domain gets muted.
This ☝️
Clients should allow Users to filter/mute by NIP05. No NIP05 then I don’t want to see your replies.
Put the onus on NIP05 providers to not allow their service to be abused by spammers lest all their community get filtered out, then spammers only have the option of doing it from their own domains which can more easily be blocked and will quickly cost too much to be worthwhile.
What are the best tools atm to achieve this? Bot filters with captchas?
Using relays with paid gateways to become whitelisted.
https://relay.nostr.com.au for example ain’t relaying Reply Guys.
Cool concept! Does that really keep out bots or just make it more expansive to run bot nets at scale?
true, it says it in the doc that it's identification, not verification. i had that twisted myself initially.