arthurfranca
9971db3551
Minor fix to nip01
2024-03-30 22:33:24 -03:00
Thebora Kompanioni
a46338bd6a
fix(docs): typo in 01.md
2024-02-08 00:03:32 +01:00
Ioan Bizău
6dd0035085
#p refers to pubkeys, *not* "event pubkeys".
2024-01-23 14:57:48 -03:00
d0812229a5
use jsonc in some places.
2024-01-21 16:08:45 -03:00
GoodDaisy
402c330ce9
Fix typo in 01.md
2024-01-05 11:59:49 +08:00
000c51ef44
Merge pull request #635 from nostr-protocol/clarify-json-serialization
...
Clarify JSON serialization for the `id` field
2023-12-29 18:15:21 -03:00
Josua Schmid
8e5a275f99
NIP-01 Tighten-up subscription_id management rule
...
Rephrase to "MUST" so that one does not assume a connection could `CLOSE` any `subscription_id`, which it must not.
2023-12-26 20:02:34 -03:00
Josua Schmid
3b065c3c04
Reword REQ for multiple filters
2023-12-26 20:54:06 +01:00
Josua Schmid
d30f03316f
Emphasis on multiple filters in NIP-01
...
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-22 14:54:17 +01:00
2bd4bf7841
CLOSED messages for relays that want to reject REQs and NIP-42 AUTH integration (#902 )
...
Co-authored-by: monlovesmango <96307647+monlovesmango@users.noreply.github.com>
2023-12-06 12:01:27 -03:00
0ba4589550
remove websocket status code meaning as it is replaced by the CLOSED message.
2023-12-02 15:05:59 -03:00
Semisol
da19c078ab
Merge branch 'master' into clarify-json-serialization
2023-11-19 01:45:41 +01:00
Semisol
4d709d1804
add form feed and backspace
2023-11-17 18:12:47 +03:00
37f6cbb775
remove all NIP authors.
2023-11-16 10:24:53 -03:00
108b7f16f9
clarify that the OK array must have 4 items.
2023-11-06 13:18:11 -03:00
b14b9d2120
nip-01: clarify that whitespace is allowed inside the strings.
...
closes https://github.com/nostr-protocol/nips/pull/861
2023-11-02 19:46:37 -03:00
b33409c099
make it clear that relays can keep multiple replaceable event versions.
2023-09-29 16:49:55 -03:00
Semisol
ea8fa91c80
clarify parameterized replaceable events
2023-09-04 14:25:04 +03:00
Semisol
c7191fc2f5
fix inconsistency
2023-09-02 14:34:39 +03:00
jiftechnify
e50bf508d9
add a-tag format for non-parameterized replaceable events
2023-08-29 23:54:09 +09:00
Yasuhiro Matsumoto
d1d438bf14
fix typo
2023-08-29 00:45:45 +09:00
Viktor Vsk
c5a8b75abd
Consistency and small refinements for NIP-01 ( #731 )
2023-08-19 23:04:55 -03:00
37c4375e29
bring back 9cac35db9b
...
fixes https://github.com/nostr-protocol/nips/issues/732
2023-08-19 23:03:23 -03:00
72bb8a128b
merge nips 12, 16, 20 and 33 into nip 01 ( #703 )
...
Co-authored-by: Viktor Vsk <me@viktorvsk.com>
2023-08-13 13:47:45 -03:00
Jesper L. Nielsen
9e0be8467d
Update 01.md
...
Spelling
2023-07-26 15:59:57 +02:00
Asai Toshiya
b503f8a92b
Clarify sort order when specified limit
2023-07-21 10:33:05 -03:00
jiftechnify
d1814405be
add detailed description of since/until
2023-07-14 12:45:46 -03:00
Yoji Shidara
0b08cf545b
Explicitly state that the subscription_id is treated per connection
2023-07-13 07:08:26 -03:00
jiftechnify
52edccbbe3
standardize the terminology
2023-07-09 07:17:08 -03:00
jiftechnify
3a32c0fd78
clarify case-sensitiveness of tag names
2023-07-09 07:17:08 -03:00
Semisol
21d71791c8
Add carriage returns and tab characters since those may be in some events
2023-07-04 13:55:15 +03:00
Semisol
3f8658ecc1
Fix typo
2023-07-04 13:49:52 +03:00
Semisol
b5a7b67d78
Clarify JSON serialization for the id field
2023-07-03 18:02:15 +03:00
tcheeric
e0fc913719
For clarification, the time unit for all date attributes in the filters (since, until) are in seconds
2023-07-02 08:41:03 -03:00
36e9fd59e9
add note about websocket status code 4000.
...
nip-01 may need some love.
2023-06-17 15:50:16 -03:00
Memory-of-Snow
2b34e9f417
Add a ',' between the 'id' and 'pubkey' elements in the JSON event in 01.md.
2023-06-12 08:16:59 -03:00
Asai Toshiya
2e842b496a
Add description for clients to kind 1
2023-06-10 07:18:28 -03:00
d435ffc39c
clarify kind:1 plaintextness.
2023-06-09 14:13:42 -03:00
Asai Toshiya
3a38583c06
Fix link to NIP-10
2023-05-31 08:43:26 -03:00
Robert C. Martin
60aa6ae168
A few changes to some nips. ( #510 )
2023-05-09 12:17:15 -03:00
89a7aa0ea0
nip01: remove misleading markdown example.
2023-05-08 11:05:58 -03:00
Josua Schmid
ee018ef8a4
Rephrase Markdown special rule
2023-05-08 11:04:34 -03:00
michaelhall923
c5f43a8f90
Update 01.md
...
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-21 10:17:36 -03:00
Yoji Shidara
4b44453626
Fix a typo; now types are EVENT, EOSE and NOTICE
2023-04-11 13:50:10 +09:00
fb5b7c739f
merge NIP-15 into NIP-01.
2023-04-09 08:50:24 -03:00
dbbf7902d9
remove tiny duplicate text
...
fixed "the the serialized event data" => "the serialized event data"
2023-03-16 20:54:00 -03:00
Semisol
b24eb78e04
Revert 'add NOTICE optional subscription_id'
...
Reverts 88009bea85
2023-03-16 17:21:57 -03:00
pablof7z
88009bea85
add NOTICE optional subscription_id
2023-03-16 13:46:08 -03:00
Josua Schmid
c74f11b7a9
Update NIP-01 to clarify pubkey reference
...
We mean to reference any public key. "the key" was a bit unspecific.
2023-03-03 18:59:37 -03:00
Mike O'Bank
5a80a906d4
Improve <subscription_id> specification
...
- "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-25 15:55:28 -03:00
