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

Update 01.md

Browse Source 
Add practical tutorial about how to partially implements the NIP-01, important for newcomers software developers.
This commit is contained in:
ionextdebug 2024-01-07 09:18:53 -03:00 committed by GitHub
parent b3c0c4f64a
commit 89fb82455e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
01.md
View File

@ -175,3 +175,8 @@ This NIP defines no rules for how `NOTICE` messages should be sent or treated.
* `["CLOSED", "sub1", "error: could not connect to the database"]` * `["CLOSED", "sub1", "error: could not connect to the database"]`
* `["CLOSED", "sub1", "error: shutting down idle subscription"]` * `["CLOSED", "sub1", "error: shutting down idle subscription"]`
- The standardized machine-readable prefixes for `OK` and `CLOSED` are: `duplicate`, `pow`, `blocked`, `rate-limited`, `invalid`, and `error` for when none of that fits. - The standardized machine-readable prefixes for `OK` and `CLOSED` are: `duplicate`, `pow`, `blocked`, `rate-limited`, `invalid`, and `error` for when none of that fits.
-----
### HOW TO
How to partially implement the NIP-01 using general purpose libraries, without NOSTR toolkits or SDKs:
[How to implement NOSTR Protocol from scratch with Python (NIP-01)](https://fullstackengineer.hashnode.dev/how-to-implement-nostr-protocol-from-scratch-with-python-nip-01)