isn't that something the relays shouldn't accept either?

For all the people who are eager to reply that Nostr should be able to handle bad practices otherwise it is already dead, or to say that "please" won't work, or these sort of comments, I must tell you that Nostr is not "antifragile", it is indeed very fragile, as all open protocols (including Bitcoi...

error fetching invoice

🫱🏼‍🫲🏽

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 co...

More examples are: kind:0 metadata fields. relay formats, REQ limits and options, and relay URL formats. It may be time for us to create a NIP working group whose task it is to evaluate all the NIP PRs, accept or deny them, and communicate to client devs in some more organized fashion. >From: fi...

The question is? How to drop events? I'm not quite sure, I'll check, if there is such a thing in nostr-relay-rs.

Maybe there should be a nostr-core, like bitcoin core, with the recent accepted consensus.

I queried many relays and found that some tags were stored with incompatible pub keys either because they were stored as bech32 or because they were just wrong. I didn’t know it would be a problem like that but I was surprised that this was happening

Agree, the Internet was built on the premise of: be liberal with what you receive, and conservative with what you send.

Having test vectors people can easily test against and maybe a more machine readable spec (e.g. JSON schema) would help with that. My experience with Nostr and LNURL has been one of reverse-engineering and trying to understand the author's intentions so far (human language sucks for specs). There's...