Your article doesn’t really capture how bad it gets. It assumes good intent - but there is an adversarial scenario that comes about the same way. I have bad memories from the browser wars, where ms did the same thing with IE. The problem is you need one well funded party with malintent to cause convergence on the client and pass the overhead on to others who simply can’t keep up. We have to protect the protocol and adherence as religiously as bitcoin.
Please do not accept invalid events in your client. Do not accept non-integer "created_at" values, do not accept non-string-array on "tags", do not accept bech32-encoded keys as tag values. Every time you do that, Nostr dies a little.
For more information on how this kills Nostr, read https://fiatjaf.com/27598e6f.html
Discussion
Yes, but how?
I don’t know. But the fact that you flagged it so early is a good start. There isn’t one answer. And the solutions I have in my head I can put out here.
*can’t
What relays is this conversation taking place on. I'm missing ever other message.
>From: fiatjaf at 03/12/23 08:15:25 on wss://relay.nostriches.org
>---------------
>Yes, but how?
Hard to know. I think my notes always have relay hints and that should help. Have you followed those?
wss://nos.lol/ is what it says.
But people are using these evil clients that do not include hints, like Iris, which is awful and breaks threads for me too sometimes.
Is somewhere described what a good Nostr client should do? Thank you