mirror of
https://github.com/nostr-protocol/nips.git
synced 2025-12-09 00:28:51 +00:00
Compare commits
4 Commits
tzidwhat
...
a6db7917f2
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
a6db7917f2 | ||
|
|
97d3531c44 | ||
|
|
f310614122 | ||
|
|
a4dadca077 |
13
18.md
13
18.md
@@ -21,9 +21,9 @@ reposted.
|
|||||||
|
|
||||||
## Quote Reposts
|
## Quote Reposts
|
||||||
|
|
||||||
Mentions to [NIP-21](21.md) entities like `nevent`, `note` and `naddr` on any
|
Mentions to [NIP-21](21.md) entities like `nevent`, `note` and `naddr` on any
|
||||||
event must be converted into `q` tags. The `q` tag ensures quote reposts are
|
event must be converted into `q` tags. The `q` tag ensures quote reposts are
|
||||||
not pulled and included as replies in threads. It also allows you to easily
|
not pulled and included as replies in threads. It also allows you to easily
|
||||||
pull and count all of the quotes for a post. The syntax follows
|
pull and count all of the quotes for a post. The syntax follows
|
||||||
|
|
||||||
`["q", "<event-id> or <event-address>", "<relay-url>", "<pubkey-if-a-regular-event>"]`
|
`["q", "<event-id> or <event-address>", "<relay-url>", "<pubkey-if-a-regular-event>"]`
|
||||||
@@ -36,3 +36,10 @@ as a "generic repost", that can include any kind of event inside other than
|
|||||||
|
|
||||||
`kind 16` reposts SHOULD contain a `"k"` tag with the stringified kind number
|
`kind 16` reposts SHOULD contain a `"k"` tag with the stringified kind number
|
||||||
of the reposted event as its value.
|
of the reposted event as its value.
|
||||||
|
|
||||||
|
When reposting a replaceable event, the repost SHOULD include an `"a"` tag with
|
||||||
|
the event coordinate (`kind:pubkey:d-tag`) of the reposted event.
|
||||||
|
|
||||||
|
If the `"a"` tag is not present, it indicates that a specific version of a replaceable
|
||||||
|
event is being reposted, in which case the `content` field must contain the full
|
||||||
|
JSON string of the reposted event.
|
||||||
|
|||||||
2
51.md
2
51.md
@@ -26,7 +26,7 @@ For example, _mute list_ can contain the public keys of spammers and bad actors
|
|||||||
| Mute list | 10000 | things the user doesn't want to see in their feeds | `"p"` (pubkeys), `"t"` (hashtags), `"word"` (lowercase string), `"e"` (threads) |
|
| Mute list | 10000 | things the user doesn't want to see in their feeds | `"p"` (pubkeys), `"t"` (hashtags), `"word"` (lowercase string), `"e"` (threads) |
|
||||||
| Pinned notes | 10001 | events the user intends to showcase in their profile page | `"e"` (kind:1 notes) |
|
| Pinned notes | 10001 | events the user intends to showcase in their profile page | `"e"` (kind:1 notes) |
|
||||||
| Read/write relays | 10002 | where a user publishes to and where they expect mentions | see [NIP-65](65.md) |
|
| Read/write relays | 10002 | where a user publishes to and where they expect mentions | see [NIP-65](65.md) |
|
||||||
| Bookmarks | 10003 | uncategorized, "global" list of things a user wants to save | `"e"` (kind:1 notes), `"a"` (kind:30023 articles), `"t"` (hashtags), `"r"` (URLs) |
|
| Bookmarks | 10003 | uncategorized, "global" list of things a user wants to save | `"e"` (kind:1 notes), `"a"` (kind:30023 articles) |
|
||||||
| Communities | 10004 | [NIP-72](72.md) communities the user belongs to | `"a"` (kind:34550 community definitions) |
|
| Communities | 10004 | [NIP-72](72.md) communities the user belongs to | `"a"` (kind:34550 community definitions) |
|
||||||
| Public chats | 10005 | [NIP-28](28.md) chat channels the user is in | `"e"` (kind:40 channel definitions) |
|
| Public chats | 10005 | [NIP-28](28.md) chat channels the user is in | `"e"` (kind:40 channel definitions) |
|
||||||
| Blocked relays | 10006 | relays clients should never connect to | `"relay"` (relay URLs) |
|
| Blocked relays | 10006 | relays clients should never connect to | `"relay"` (relay URLs) |
|
||||||
|
|||||||
7
52.md
7
52.md
@@ -65,8 +65,6 @@ Example:
|
|||||||
["d", "<random-identifier>"],
|
["d", "<random-identifier>"],
|
||||||
|
|
||||||
["title", "<title of calendar event>"],
|
["title", "<title of calendar event>"],
|
||||||
["summary", "<brief description of the calendar event>"],
|
|
||||||
["image", "<string with image URI>"],
|
|
||||||
|
|
||||||
// dates
|
// dates
|
||||||
["start", "<YYYY-MM-DD>"],
|
["start", "<YYYY-MM-DD>"],
|
||||||
@@ -95,6 +93,8 @@ Aside from the common tags, this also takes the following tags:
|
|||||||
|
|
||||||
* `start` (required) inclusive start Unix timestamp in seconds. Must be less than `end`, if it exists.
|
* `start` (required) inclusive start Unix timestamp in seconds. Must be less than `end`, if it exists.
|
||||||
* `end` (optional) exclusive end Unix timestamp in seconds. If omitted, the calendar event ends instantaneously.
|
* `end` (optional) exclusive end Unix timestamp in seconds. If omitted, the calendar event ends instantaneously.
|
||||||
|
* `start_tzid` (optional) time zone of the start timestamp, as defined by the IANA Time Zone Database. e.g., `America/Costa_Rica`
|
||||||
|
* `end_tzid` (optional) time zone of the end timestamp, as defined by the IANA Time Zone Database. e.g., `America/Costa_Rica`. If omitted and `start_tzid` is provided, the time zone of the end timestamp is the same as the start timestamp.
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
{
|
{
|
||||||
@@ -114,6 +114,9 @@ Aside from the common tags, this also takes the following tags:
|
|||||||
["start", "<unix timestamp in seconds>"],
|
["start", "<unix timestamp in seconds>"],
|
||||||
["end", "<unix timestamp in seconds>"],
|
["end", "<unix timestamp in seconds>"],
|
||||||
|
|
||||||
|
["start_tzid", "<IANA Time Zone Database identifier>"],
|
||||||
|
["end_tzid", "<IANA Time Zone Database identifier>"],
|
||||||
|
|
||||||
// location
|
// location
|
||||||
["location", "<location>"],
|
["location", "<location>"],
|
||||||
["g", "<geohash>"],
|
["g", "<geohash>"],
|
||||||
|
|||||||
Reference in New Issue
Block a user