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
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 only so much time people spend on spec compliance if it works(tm), being compliant should be the easiest path to "it works".
The current specs could be much better even if sticking to "human language". E.g., nowhere does NIP-01 say that created_at must be an integer, yet to #[2] that is apparently obvious. All NIP-01 says is that it's a unix timestamp in seconds. Go to the Wikipedia page for Unix time, and you'll see several non-integer examples.
Test vectors that cover all kinds of corner cases would definitely help.
Please send a PR!
Good points. What is a good way to present the test vectors so it's easy for people to check their implementations?
Might be off topic or perhaps not in a way, but I wonder what people’s thoughts are on technological future functions to assist male performance/enhancement to not lack when we have to use to substitute vibrators? Or thoughts on brain implants?
Especially when they are “lacking presence” too apparently pahahaha but keep pretending they’ve got shit going on while I keep looking for something more exciting in my life.
