100%
right now there's an obvious incentive to do it because almost all clients are super naive; being not-naive is extremely costly
once this is not the case, the incentive goes away
(that said, you *can* identify pubkeys using it for everything and ban/rate-limit their writes), but that's costly on it's own; I doubt that will be needed
I see blastr like my https://t.me/pingstr_bot bot... a stop-gap solution to patch something that will be better solved later
The better solution that replaces Blastr would be NIP-65 if i’m not mistaken, no?
yeah, in general every practice that makes clients smarter with regard to where to read and write events instead of just connecting to everything they've been explicitly configured to and disregarding NIP-65, tags, etc
