upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
path: root/01.md
AgeCommit message (Collapse)Author
2024-09-30Clarify tag filtersJon Staab
2024-09-28complete renaming to "addressable" events.fiatjaf
as noticed by @bezysoftware at https://github.com/nostr-protocol/nips/pull/1437#issuecomment-2380626514. I don't know how so many of these instances were left from the original PR at following ca3c52e3e74f0a4679f1c6c0d9ac6461ea748d2d.
2024-08-31Merge pull request #1333 from coracle-social/clarify-nip01hodlbod
Clarify what happens when a duplicate subscription is sent, remove CLOSED on duplicate subscription
2024-08-20rename "parameterized replaceable event" to "addressable event" (#1418)fiatjaf_
2024-07-18NIP-01: sort events by id after created_atAlex Gleason
2024-07-06More precisely document since/until bounds. (#1284)Cody Casterline
* More precisely document since/until bounds. Lower in this document, this is expressed as "since <= created_at <= until". But the English description said that these values had to be "newer than" or "older than". These two were in conflict. I assume the inclusive behavior is the intended one, since that documentation was added later to clarify. This just makes both cases match. * Update 01.md Co-authored-by: Alex Gleason <alex@alexgleason.me> * Update 01.md Co-authored-by: Alex Gleason <alex@alexgleason.me> --------- Co-authored-by: Alex Gleason <alex@alexgleason.me>
2024-06-27Clarify what happens when a duplicate subscription is sent, remove CLOSED on ↵Jon Staab
duplicate subscription
2024-06-23Clarify which kinds have lifetime of 'regular' (#1315)Arjen Stens
* Clarify which kinds have lifetime of 'regular' * Missed space * Document kind 41 as replaceable * Revert "Document kind 41 as replaceable" This reverts commit eead2f5a749cfee6de131944e0e73350759e28b4.
2024-06-17"user metadata" and fix table on readme.fiatjaf
2024-06-17Merge pull request #1309 from ArmanTheParman/patch-2hodlbod
metadata clarity.md
2024-06-16parentheses > commas (#1308)Arman The Parman
* Update 01.md A few small changes that can potentially help a broader audience (non-developers) follow the meaning. * monospace hex Co-authored-by: Asai Toshiya <to.asai.60@gmail.com> --------- Co-authored-by: fiatjaf_ <fiatjaf@gmail.com> Co-authored-by: Asai Toshiya <to.asai.60@gmail.com>
2024-06-16Update 01.mdArman The Parman
This is not a correction but a suggestion... When I first read it, it wasn't clear that metadata is specifically for a user and not inclusive of other things (eg not metadata about a photo). Adding this one extra word here would have helped me understand that immediately.
2024-06-15Update 01.mdArman The Parman
Small grammatical change for easier reading
2024-05-24Update 01.mdhodlbod
Co-authored-by: Asai Toshiya <to.asai.60@gmail.com>
2024-05-24nip01: mention extra metadata fields may be setP. Reis
2024-04-30Require tags to have at least one stringLeo Wandersleb
fixes #1193
2024-03-30Minor fix to nip01arthurfranca
2024-02-08fix(docs): typo in 01.mdThebora Kompanioni
2024-01-23#p refers to pubkeys, *not* "event pubkeys".Ioan Bizău
2024-01-21use jsonc in some places.fiatjaf
2024-01-05Fix typo in 01.mdGoodDaisy
2023-12-29Merge pull request #635 from nostr-protocol/clarify-json-serializationfiatjaf_
Clarify JSON serialization for the `id` field
2023-12-26NIP-01 Tighten-up subscription_id management ruleJosua Schmid
Rephrase to "MUST" so that one does not assume a connection could `CLOSE` any `subscription_id`, which it must not.
2023-12-26Reword REQ for multiple filtersJosua Schmid
2023-12-22Emphasis on multiple filters in NIP-01Josua Schmid
As mentioned further down in NIP-01 > A REQ message may contain multiple filters. The comma makes it more clear that the message array can container more than 3 items. So it is understood easily to match ``` // correct: ["REQ", <subscription_id>, filters1, filters2, …] ``` instead of ``` // wrong: ["REQ", <subscription_id>, [filters1, filters2, …]] ```
2023-12-06`CLOSED` messages for relays that want to reject REQs and NIP-42 `AUTH` ↵fiatjaf_
integration (#902) Co-authored-by: monlovesmango <96307647+monlovesmango@users.noreply.github.com>
2023-12-02remove websocket status code meaning as it is replaced by the CLOSED message.fiatjaf
2023-11-19Merge branch 'master' into clarify-json-serializationSemisol
2023-11-17add form feed and backspaceSemisol
2023-11-16remove all NIP authors.fiatjaf
2023-11-06clarify that the OK array must have 4 items.fiatjaf
2023-11-02nip-01: clarify that whitespace is allowed inside the strings.fiatjaf
closes https://github.com/nostr-protocol/nips/pull/861
2023-09-29make it clear that relays can keep multiple replaceable event versions.fiatjaf
2023-09-04clarify parameterized replaceable eventsSemisol
2023-09-02fix inconsistencySemisol
2023-08-29add a-tag format for non-parameterized replaceable eventsjiftechnify
2023-08-29fix typoYasuhiro Matsumoto
2023-08-19Consistency and small refinements for NIP-01 (#731)Viktor Vsk
2023-08-19bring back 9cac35db9b1d41c8eb7413269308a76687489b30fiatjaf
fixes https://github.com/nostr-protocol/nips/issues/732
2023-08-13merge nips 12, 16, 20 and 33 into nip 01 (#703)fiatjaf_
Co-authored-by: Viktor Vsk <me@viktorvsk.com>
2023-07-26Update 01.mdJesper L. Nielsen
Spelling
2023-07-21Clarify sort order when specified limitAsai Toshiya
2023-07-14add detailed description of since/untiljiftechnify
2023-07-13Explicitly state that the `subscription_id` is treated per connectionYoji Shidara
2023-07-09standardize the terminologyjiftechnify
2023-07-09clarify case-sensitiveness of tag namesjiftechnify
2023-07-04Add carriage returns and tab characters since those may be in some eventsSemisol
2023-07-04Fix typoSemisol
2023-07-03Clarify JSON serialization for the `id` fieldSemisol
2023-07-02For clarification, the time unit for all date attributes in the filters ↵tcheeric
(since, until) are in seconds
2023-06-17add note about websocket status code 4000.fiatjaf
nip-01 may need some love.
2023-06-12Add a ',' between the 'id' and 'pubkey' elements in the JSON event in 01.md.Memory-of-Snow
2023-06-10Add description for clients to kind 1Asai Toshiya
2023-06-09clarify kind:1 plaintextness.fiatjaf
2023-05-31Fix link to NIP-10Asai Toshiya
2023-05-09A few changes to some nips. (#510)Robert C. Martin
2023-05-08nip01: remove misleading markdown example.fiatjaf
2023-05-08Rephrase Markdown special ruleJosua Schmid
2023-04-21Update 01.mdmichaelhall923
Info on "e" and "p" tags is kind of hard to find so I added a link to it in the place that I intuitively looked for it.
2023-04-11Fix a typo; now types are EVENT, EOSE and NOTICEYoji Shidara
2023-04-09merge NIP-15 into NIP-01.fiatjaf
2023-03-16remove tiny duplicate textSepehr Safari
fixed "the the serialized event data" => "the serialized event data"
2023-03-16Revert 'add NOTICE optional subscription_id'Semisol
Reverts 88009bea8509d004672551be7346a03c373491d0
2023-03-16add NOTICE optional subscription_idpablof7z
2023-03-03Update NIP-01 to clarify pubkey referenceJosua Schmid
We mean to reference any public key. "the key" was a bit unspecific.
2023-02-25Improve `<subscription_id>` specificationMike O'Bank
- "random" is not an accurate description - I've noticed long (sha256 hashes in hex) being rejected by some relays. So there seems a need to specify a max length. - "non empty", cause an empty string could be interpreted as `null` To be decided: - Max length number - Are `subscription_id`s case sensitive? - Will `subscription_id`s be white space trimmed?
2023-02-25explicitly prohibit markdown on kind:1.fiatjaf
2023-02-08Added clarification for signature to be in hexJimmy Song
2023-01-25Update NIP-01 to clarify since and until filtersBen Franks
The since and until filters does not clarify integer format and some relays fail to recognize filters with a float based timestamp.
2023-01-21specify lowercase on nip01 event hex fields.fiatjaf
2022-12-26Minor grammar fixessgmoore
Minor grammar fix at line 13, 83, 85. and 111.
2022-12-24LUD-01: fix typo for the desc of event kind 2Hampus Sjöberg
2022-12-15Remove username pattern requirementsJon Staab
Most implementation ignore this line. Enforcing that usernames not include spaces, special chracters, unicode, emojis, etc has no benefit and is unnecessarily user hostile.
2022-12-08Clarify use of kind 1 and kind 1000-10000Jonathan Staab
2022-12-02nip-01: improve connection/subscriptions recommendation and remove the ↵fiatjaf
ill-advised 3 subscriptions limit.
2022-11-15Reword NIP-01 to clarify no line breaks. Existing language of "indentation" ↵Mike Dilger
implies line breaks.
2022-11-04Fix regex for SetMetadata in NIP1w3irdrobot
It appears the regex given in NIP1 for setting the username in the setmetadata event was slightly off. I think the fix here is what was intended. Though I think what was meant here was pretty obvious, to make it easier on future developers, I updated the regex to something that should work with just copying and pasting.
2022-10-26Update 01.mdDZ
fix indentation
2022-10-07Update 01.mdDZ
fix typo
2022-06-21Fix some typos and adds json type to code blocksemeceve
2022-06-09update nip-02 to disallow `null`, only allow strings in tags.fiatjaf
fixes https://github.com/nostr-protocol/nips/pull/15 fixes https://github.com/fiatjaf/nostr-army-knife/issues/2 fixes https://github.com/fiatjaf/relayer/issues/3
2022-06-05update to nip01 to specify syntax for usernames.Robert C. Martin
2022-05-08sneak filter.limit in nip-01.fiatjaf
2022-05-01migrate nips from main nostr repo.fiatjaf