NIP-D3: DMZ Kinds

[kehiy]

This NIP reserves 20 kinds for use-cases that may not want to be standard. It can be anything but in my mind it will be mostly specific apps for specific group of people maybe. It can be internal or external tools and apps.

Why this?

1. It helps them to prevent using non-reserved kinds that may later be used by new NIPs.
2. Relays can block them and be sure they don't need them.
3. Since Nostr can use a generalized server (relays) to achieve a lot of functionalities, its a good option for a rapid development of apps, but not all apps want to be standards.

They can also be used for testing.

[pablof7z]

cNACK

If people want to make things that are not standard they should a) use something else, b) use relays that AUTH and are exclusively for whatever use and they can use whatever kind they want

Also, if a bunch of apps use the same kind numbers for a bunch of completely different use cases with different schemas they will already be breaking each others' stuff and having to code extremely defensively anyway, so segregating by relay instead of by kind is already necessary anyway.

[pablof7z]

I do like the fact that this implies the rest of nostr is militarized though.

[kehiy]

@pablof7z These stuff makes sense too, but this idea is actually too young in my mind, so let me think more about it.

Thanks. 🫡

[Giszmo]

cNACK

I see no sense in standardizing which kinds will not be standardized. All apps already have to assume that other apps use the kinds they use in different ways and should there ever be a class of apps that use nostr but only in their closed apps ... why should we care about them in our standardization document. They can use type: instead of kind: for all I care.

[derekross]

NACK.

Making a standard for non-standards doesn't make sense. It becomes standard at that point.