diff options
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 17 |
1 files changed, 10 insertions, 7 deletions
| @@ -54,14 +54,15 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos | |||
| 54 | - [NIP-34: `git` stuff](34.md) | 54 | - [NIP-34: `git` stuff](34.md) |
| 55 | - [NIP-35: Torrents](35.md) | 55 | - [NIP-35: Torrents](35.md) |
| 56 | - [NIP-36: Sensitive Content](36.md) | 56 | - [NIP-36: Sensitive Content](36.md) |
| 57 | - [NIP-37: Draft Events](37.md) | ||
| 57 | - [NIP-38: User Statuses](38.md) | 58 | - [NIP-38: User Statuses](38.md) |
| 58 | - [NIP-39: External Identities in Profiles](39.md) | 59 | - [NIP-39: External Identities in Profiles](39.md) |
| 59 | - [NIP-40: Expiration Timestamp](40.md) | 60 | - [NIP-40: Expiration Timestamp](40.md) |
| 60 | - [NIP-42: Authentication of clients to relays](42.md) | 61 | - [NIP-42: Authentication of clients to relays](42.md) |
| 61 | - [NIP-44: Versioned Encryption](44.md) | 62 | - [NIP-44: Encrypted Payloads (Versioned)](44.md) |
| 62 | - [NIP-45: Counting results](45.md) | 63 | - [NIP-45: Counting results](45.md) |
| 63 | - [NIP-46: Nostr Connect](46.md) | 64 | - [NIP-46: Nostr Remote Signing](46.md) |
| 64 | - [NIP-47: Wallet Connect](47.md) | 65 | - [NIP-47: Nostr Wallet Connect](47.md) |
| 65 | - [NIP-48: Proxy Tags](48.md) | 66 | - [NIP-48: Proxy Tags](48.md) |
| 66 | - [NIP-49: Private Key Encryption](49.md) | 67 | - [NIP-49: Private Key Encryption](49.md) |
| 67 | - [NIP-50: Search Capability](50.md) | 68 | - [NIP-50: Search Capability](50.md) |
| @@ -169,6 +170,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos | |||
| 169 | | `10006` | Blocked relays list | [51](51.md) | | 170 | | `10006` | Blocked relays list | [51](51.md) | |
| 170 | | `10007` | Search relays list | [51](51.md) | | 171 | | `10007` | Search relays list | [51](51.md) | |
| 171 | | `10009` | User groups | [51](51.md), [29](29.md) | | 172 | | `10009` | User groups | [51](51.md), [29](29.md) | |
| 173 | | `10013` | Draft relays | [37](37.md) | | ||
| 172 | | `10015` | Interests list | [51](51.md) | | 174 | | `10015` | Interests list | [51](51.md) | |
| 173 | | `10019` | Nutzap Mint Recommendation | [61](61.md) | | 175 | | `10019` | Nutzap Mint Recommendation | [61](61.md) | |
| 174 | | `10030` | User emoji list | [51](51.md) | | 176 | | `10030` | User emoji list | [51](51.md) | |
| @@ -213,6 +215,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos | |||
| 213 | | `30618` | Repository state announcements | [34](34.md) | | 215 | | `30618` | Repository state announcements | [34](34.md) | |
| 214 | | `30818` | Wiki article | [54](54.md) | | 216 | | `30818` | Wiki article | [54](54.md) | |
| 215 | | `30819` | Redirects | [54](54.md) | | 217 | | `30819` | Redirects | [54](54.md) | |
| 218 | | `31234` | Draft Event | [37](37.md) | | ||
| 216 | | `31388` | Link Set | [Corny Chat][cornychat-linkset] | | 219 | | `31388` | Link Set | [Corny Chat][cornychat-linkset] | |
| 217 | | `31890` | Feed | [NUD: Custom Feeds][NUD: Custom Feeds] | | 220 | | `31890` | Feed | [NUD: Custom Feeds][NUD: Custom Feeds] | |
| 218 | | `31922` | Date-Based Calendar Event | [52](52.md) | | 221 | | `31922` | Date-Based Calendar Event | [52](52.md) | |
| @@ -282,8 +285,8 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos | |||
| 282 | | `l` | label, label namespace | -- | [32](32.md) | | 285 | | `l` | label, label namespace | -- | [32](32.md) | |
| 283 | | `L` | label namespace | -- | [32](32.md) | | 286 | | `L` | label namespace | -- | [32](32.md) | |
| 284 | | `m` | MIME type | -- | [94](94.md) | | 287 | | `m` | MIME type | -- | [94](94.md) | |
| 285 | | `p` | pubkey (hex) | relay URL, petname | [01](01.md), [02](02.md) | | 288 | | `p` | pubkey (hex) | relay URL, petname | [01](01.md), [02](02.md), [22](22.md) | |
| 286 | | `P` | pubkey (hex) | -- | [57](57.md) | | 289 | | `P` | pubkey (hex) | -- | [22](22.md), [57](57.md) | |
| 287 | | `q` | event id (hex) | relay URL, pubkey (hex) | [18](18.md) | | 290 | | `q` | event id (hex) | relay URL, pubkey (hex) | [18](18.md) | |
| 288 | | `r` | a reference (URL, etc) | -- | [24](24.md), [25](25.md) | | 291 | | `r` | a reference (URL, etc) | -- | [24](24.md), [25](25.md) | |
| 289 | | `r` | relay url | marker | [65](65.md) | | 292 | | `r` | relay url | marker | [65](65.md) | |
| @@ -341,9 +344,9 @@ Please update these lists when proposing new NIPs. | |||
| 341 | 344 | ||
| 342 | ## Is this repository a centralizing factor? | 345 | ## Is this repository a centralizing factor? |
| 343 | 346 | ||
| 344 | To promote interoperability, we standards that everybody can follow, and we need them to define a **single way of doing each thing** without ever hurting **backwards-compatibility**, and for that purpose there is no way around getting everybody to agree on the same thing and keep a centralized index of these standards. However the fact that such index exists doesn't hurt the decentralization of Nostr. _At any point the central index can be challenged if it is failing to fulfill the needs of the protocol_ and it can migrate to other places and be maintained by other people. | 347 | To promote interoperability, we need standards that everybody can follow, and we need them to define a **single way of doing each thing** without ever hurting **backwards-compatibility**, and for that purpose there is no way around getting everybody to agree on the same thing and keep a centralized index of these standards. However the fact that such an index exists doesn't hurt the decentralization of Nostr. _At any point the central index can be challenged if it is failing to fulfill the needs of the protocol_ and it can migrate to other places and be maintained by other people. |
| 345 | 348 | ||
| 346 | It can even fork into multiple and then some clients would go one way, others would go another way, and some clients would adhere to both competing standards. This would hurt the simplicity, openness and interoperability of Nostr a little, but everything would still work in the short term. | 349 | It can even fork into multiple versions, and then some clients would go one way, others would go another way, and some clients would adhere to both competing standards. This would hurt the simplicity, openness and interoperability of Nostr a little, but everything would still work in the short term. |
| 347 | 350 | ||
| 348 | There is a list of notable Nostr software developers who have commit access to this repository, but that exists mostly for practical reasons, as by the nature of the thing we're dealing with the repository owner can revoke membership and rewrite history as they want -- and if these actions are unjustified or perceived as bad or evil the community must react. | 351 | There is a list of notable Nostr software developers who have commit access to this repository, but that exists mostly for practical reasons, as by the nature of the thing we're dealing with the repository owner can revoke membership and rewrite history as they want -- and if these actions are unjustified or perceived as bad or evil the community must react. |
| 349 | 352 | ||