nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 08:25:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Mark key NIPs as 'final'

Browse Source
This commit is contained in:
Michael Jurkoic 2024-03-11 21:12:10 -05:00
parent 9e9ae1eb88
commit a41a7ec855
10 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
01.md
View File

@ -4,7 +4,7 @@ NIP-01
Basic protocol flow description Basic protocol flow description
------------------------------- -------------------------------
`draft` `mandatory` `final` `mandatory`
This NIP defines the basic protocol that should be implemented by everybody. New NIPs may add new optional (or mandatory) fields and messages and features to the structures and flows described here. This NIP defines the basic protocol that should be implemented by everybody. New NIPs may add new optional (or mandatory) fields and messages and features to the structures and flows described here.

2
07.md
View File

@ -4,7 +4,7 @@ NIP-07
`window.nostr` capability for web browsers `window.nostr` capability for web browsers
------------------------------------------ ------------------------------------------
`draft` `optional` `final` `optional`
The `window.nostr` object may be made available by web browsers or extensions and websites or web-apps may make use of it after checking its availability. The `window.nostr` object may be made available by web browsers or extensions and websites or web-apps may make use of it after checking its availability.

2
10.md
View File

@ -5,7 +5,7 @@ NIP-10
On "e" and "p" tags in Text Events (kind 1). On "e" and "p" tags in Text Events (kind 1).
-------------------------------------------- --------------------------------------------
`draft` `optional` `final` `optional`
## Abstract ## Abstract
This NIP describes how to use "e" and "p" tags in text events, especially those that are replies to other text events. It helps clients thread the replies into a tree rooted at the original event. This NIP describes how to use "e" and "p" tags in text events, especially those that are replies to other text events. It helps clients thread the replies into a tree rooted at the original event.

2
18.md
View File

@ -4,7 +4,7 @@ NIP-18
Reposts Reposts
------- -------
`draft` `optional` `final` `optional`
A repost is a `kind 6` event that is used to signal to followers A repost is a `kind 6` event that is used to signal to followers
that a `kind 1` text note is worth reading. that a `kind 1` text note is worth reading.

2
21.md
View File

@ -4,7 +4,7 @@ NIP-21
`nostr:` URI scheme `nostr:` URI scheme
------------------- -------------------
`draft` `optional` `final` `optional`
This NIP standardizes the usage of a common URI scheme for maximum interoperability and openness in the network. This NIP standardizes the usage of a common URI scheme for maximum interoperability and openness in the network.

2
23.md
View File

@ -4,7 +4,7 @@ NIP-23
Long-form Content Long-form Content
----------------- -----------------
`draft` `optional` `final` `optional`
This NIP defines `kind:30023` (a _parameterized replaceable event_) for long-form text content, generally referred to as "articles" or "blog posts". `kind:30024` has the same structure as `kind:30023` and is used to save long form drafts. This NIP defines `kind:30023` (a _parameterized replaceable event_) for long-form text content, generally referred to as "articles" or "blog posts". `kind:30024` has the same structure as `kind:30023` and is used to save long form drafts.

2
25.md
View File

@ -5,7 +5,7 @@ NIP-25
Reactions Reactions
--------- ---------
`draft` `optional` `final` `optional`
A reaction is a `kind 7` event that is used to react to other events. A reaction is a `kind 7` event that is used to react to other events.

2
36.md
View File

@ -4,7 +4,7 @@ NIP-36
Sensitive Content / Content Warning Sensitive Content / Content Warning
----------------------------------- -----------------------------------
`draft` `optional` `final` `optional`
The `content-warning` tag enables users to specify if the event's content needs to be approved by readers to be shown. The `content-warning` tag enables users to specify if the event's content needs to be approved by readers to be shown.
Clients can hide the content until the user acts on it. Clients can hide the content until the user acts on it.

2
38.md
View File

@ -5,7 +5,7 @@ NIP-38
User Statuses User Statuses
-------------- --------------
`draft` `optional` `final` `optional`
## Abstract ## Abstract

2
57.md
View File

@ -4,7 +4,7 @@ NIP-57
Lightning Zaps Lightning Zaps
-------------- --------------
`draft` `optional` `final` `optional`
This NIP defines two new event types for recording lightning payments between users. `9734` is a `zap request`, representing a payer's request to a recipient's lightning wallet for an invoice. `9735` is a `zap receipt`, representing the confirmation by the recipient's lightning wallet that the invoice issued in response to a `zap request` has been paid. This NIP defines two new event types for recording lightning payments between users. `9734` is a `zap request`, representing a payer's request to a recipient's lightning wallet for an invoice. `9735` is a `zap receipt`, representing the confirmation by the recipient's lightning wallet that the invoice issued in response to a `zap request` has been paid.