With NIP17 there is no way to defend at least against an attack where the sender generates a lot of msgs and you have to decrypt(unwrap) each before you can decide what to do with it.

Relays can't do anything about this either, as mentioned before. No one knows who you are - i.e. WoT is useless here, if we look merely on event info.

The method of relay AUTH and then DM, although interesting, falls short too:

1. **Most ppl won't have a 10050**

2. Hard to standardize. Okay, we could try to craft another spec for this too. But still there is point 1.

The solution, again, is not overengineering a DOA solution.

Just use communities.

If you share at least one community, it's gonna be allowed by default.

Communities CAN and WILL run relays, for DMs as well. They care about their members getting their mail, and to effectively filter spam as well. Yes, we can do more complex stuff later when we need.

This kind of stuff is NOT solved by clients, NOR by relays. It's solved by people with the right incentives.