add unrecommended tag and warning to NIP bodies.

This commit is contained in:
fiatjaf
2026-05-31 08:10:27 -03:00
parent 4f494afd7f
commit 5491bd5c63
10 changed files with 25 additions and 10 deletions

4
03.md
View File

@@ -1,10 +1,12 @@
> __Warning__ `unrecommended`: vulnerable to one specific attack, needs update
NIP-03
======
OpenTimestamps Attestations for Events
--------------------------------------
`draft` `optional`
`draft` `unrecommended` `optional`
This NIP defines an event with `kind:1040` that can contain an [OpenTimestamps](https://opentimestamps.org/) proof for any other event:

4
06.md
View File

@@ -1,10 +1,12 @@
> __Warning__ `unrecommended`: prefer a single nsec
NIP-06
======
Basic key derivation from mnemonic seed phrase
----------------------------------------------
`draft` `optional`
`draft` `unrecommended` `optional`
[BIP39](https://bips.xyz/39) is used to generate mnemonic seed words and derive a binary seed from them.

4
15.md
View File

@@ -1,10 +1,12 @@
> __Warning__ `unrecommended`: too complicated, try [99](99.md) instead
NIP-15
======
Nostr Marketplace
-----------------
`draft` `optional`
`draft` `unrecommended` `optional`
Based on [Diagon-Alley](https://github.com/lnbits/Diagon-Alley).

2
26.md
View File

@@ -6,7 +6,7 @@ NIP-26
Delegated Event Signing
-----------------------
`draft` `optional` `relay`
`draft` `unrecommended` `optional` `relay`
This NIP defines how events can be delegated so that they can be signed by other keypairs.

3
28.md
View File

@@ -1,3 +1,4 @@
> __Warning__ `unrecommended`: try [NIP-29](29.md) instead
NIP-28
======
@@ -5,7 +6,7 @@ NIP-28
Public Chat
-----------
`draft` `optional`
`draft` `unrecommended` `optional`
This NIP defines new event kinds for public chat channels, channel messages, and basic client-side moderation.

4
31.md
View File

@@ -1,10 +1,12 @@
> __Warning__ `unrecommended`: unnecessarily bloated
NIP-31
======
Dealing with unknown event kinds
--------------------------------
`draft` `optional`
`draft` `unrecommended` `optional`
When creating a new custom event kind that is part of a custom protocol and isn't meant to be read as text (like `kind:1`), clients should use an `alt` tag to write a short human-readable plaintext summary of what that event is about.

4
72.md
View File

@@ -1,10 +1,12 @@
> __Warning__ `unrecommended`: try [NIP-29](29.md) instead
NIP-72
======
Moderated Communities (Reddit Style)
------------------------------------
`draft` `optional`
`draft` `unrecommended` `optional`
The goal of this NIP is to enable public communities. It defines the replaceable event `kind:34550` to define the community and the current list of moderators/administrators. Users that want to post into the community, simply tag any Nostr event with the community's `a` tag. Moderators may issue an approval event `kind:4550`.

4
90.md
View File

@@ -1,10 +1,12 @@
> __Warning__ `unrecommended`: this got totally out of control, prefer use-case-specific microstandards
NIP-90
======
Data Vending Machine
--------------------
`draft` `optional`
`draft` `unrecommended` `optional`
This NIP defines the interaction between customers and Service Providers for performing on-demand computation.

2
96.md
View File

@@ -6,7 +6,7 @@ NIP-96
HTTP File Storage Integration
-----------------------------
`draft` `optional`
`draft` `unrecommended` `optional`
## Introduction

4
BE.md
View File

@@ -1,10 +1,12 @@
> __Warning__ `unrecommended`: only implemented once and unclear whether it works, requires review
NIP-BE
======
Nostr BLE Communications Protocol
---------------------------------
`draft` `optional`
`draft` `unrecommended` `optional`
This NIP specifies how Nostr apps can use BLE to communicate and synchronize with each other. The BLE protocol follows a client-server pattern, so this NIP emulates the WS structure in a similar way, but with some adaptations to its limitations.