If someone's allying with a domain that spams my periphery with noise, i really don't care about them and wouldn't bother validating their signal as a user in the first place. Being able to have a nostr address point to so many free domains, and they choose the spammy one? No thanks, i'd rather block the domain by default. If they want to be seen by me, they're welcome to do the "work" and change out their address.

On my freemium offering at NostrAddress.com it puts the free requests into an hourly batch before their address is live. It has mostly helped stop bots and bad actors as they don’t get the address immediately and have to wait. On the relay side of things, after the reply guy spam, I introduced nip05 validation on Nosflare. This let you block any event who’s author didn’t have a valid nip05 and you could also block specific nip05 domains. I knew in the future there would be spam bots who would have nip05s. It’s all a cat and mouse, whack-a-mole lol

Its a bidirectional relationship as well. Maybe I only want to communicate/see users from @mynostrcommunity.com or want to block anyone that does/nt have a NIP-05. Its about enabling optionality and multiple types of barriers. What ultimately makes nostr robust as a whole ecosystem is that there's no single criteria to game. You'll break nostr eventually if there's a singular best & unchangingWoT metric that all relays and clients use. Good luck doing that when every user, relay and client have even 10's of WoT algorithms to choose from.