Alex Gleason

Doesn't really matter, but I lean towards not changing it. I believe the NIPs should be somewhere between a cold specification and a For Dummies book. This is a little...

And actually, kind 1 Notes are the "N" in "Nostr". It would be a disservice not to include it in NIP-01. What might make more sense is to add an...

Acknowledged, but moving it to NIP-10 deemphasizes it too much. Kind 1 events should still be defined in NIP-01. NIP-01 is mandatory, but the text itself can explain that kind...

@vitorpamplona That sounds reasonable to me. I like the direction with NIP-10. With NIP-01, just remember that N and OS exist alongside each other, N is not part of OS....

@vitorpamplona You can run `nak req -k 30382 -a db0e60d10b9555a39050c258d460c5c461f6d18f467aa9f62de1a728b8a891a4 wss://gleasonator.dev/relay` to see my events. I am using custom `n` values, none of which are described here. Example: ```json {...

Here's a cool thing. Deno is similar to Node, except you can import modules by URL. With this, it's possible to import JavaScript files hosted on Nostr directly into Deno...

This is related to #523 #683 The new Groups NIP has separate kinds for replies. Not sure I agree with it.

Shouldn't we at least include the namespace in the third position of the tag? eg `["l", "en-US", "ISO-3166-2"]`

Language should not be `en-US`, ideally it should be just `en` marked with `ISO-639-1` I want to be able to distinguish between `["l", "en-US", "ISO-3166-2"]` and `["l", "en", "ISO-639-1"]`

Why not use [NIP-98](https://github.com/nostr-protocol/nips/blob/master/98.md)? EDIT: I see NIP-98 is already a part of this. I don't understand what this is solving.