From 9b7cabddf3204080d50d07dc757dcd6b9653d97a Mon Sep 17 00:00:00 2001 From: sepehr-safari Date: Fri, 18 Sep 2026 20:45:14 +0300 Subject: [PATCH] The t tag row says what shipped Hashtags have worked since v0.19.0 and the page still called them planned. This is the fourth stale row, left out of the last change because that one was about three and I did not want to widen it silently. It does more than the old row implied, so the new one says both halves. Pressing a hashtag opens the notes carrying it, read from the local store first and then asked of relays. And a `t` tag is written onto notes you post, so yours are findable by the same query. Checked in the code before writing it here rather than from the release notes: a store query on `letter = 't'`, a relay filter on the same, and the tag being appended when a note is assembled. The other NIP-24 row, extra `kind:0` fields carried through a profile rewrite, is genuinely still planned and stays where it is. --- content/nips.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nips.mdx b/content/nips.mdx index 6009df5..61b3339 100644 --- a/content/nips.mdx +++ b/content/nips.mdx @@ -34,6 +34,7 @@ rather than library surface. | [10](https://github.com/nostr-protocol/nips/blob/master/10.md) | Reply threading, marked `e` tags | threads, and replies you post | | [18](https://github.com/nostr-protocol/nips/blob/master/18.md) | Reposts, `kind:6` and `kind:16` | counted on a note, and a row in notifications | | [22](https://github.com/nostr-protocol/nips/blob/master/22.md) | Comments, `kind:1111`, the other way to write a reply | read in threads, on a profile, and as a notification | +| [24](https://github.com/nostr-protocol/nips/blob/master/24.md) | The `t` tag: a hashtag is a lowercase `t`, and NIP-01 single-letter indexing is what makes `#t` queryable | pressing one opens the notes carrying it, read from this machine first and then asked of relays. Written onto notes you post, so yours are findable too | | [25](https://github.com/nostr-protocol/nips/blob/master/25.md) | Reactions, `kind:7` | likes, in the feed and notifications | | [27](https://github.com/nostr-protocol/nips/blob/master/27.md) | `nostr:` mentions in content | names instead of raw base32 | | [89](https://github.com/nostr-protocol/nips/blob/master/89.md) | Application handlers | the `client` tag on notes you post | @@ -54,7 +55,6 @@ it. |----|----|----|----| | [NIP-24](https://github.com/nostr-protocol/nips/blob/master/24.md) | Extra `kind:0` fields (`display_name`, `website`, `banner`, `bot`, `birthday`), carried through untouched when I rewrite a profile | Your identity, and your key | 🚧 planned | | [NIP-50](https://github.com/nostr-protocol/nips/blob/master/50.md) | Search, which is a relay-side feature: a `search` string on an ordinary filter | Find anything, and keep it clean | 🚧 planned | -| [NIP-24](https://github.com/nostr-protocol/nips/blob/master/24.md) | The `t` tag: a hashtag is a lowercase `t`, and NIP-01 single-letter indexing is what makes `#t` queryable | Find anything, and keep it clean | 🚧 planned | | [Blossom BUD-02](https://github.com/hzrd149/blossom/blob/master/buds/02.md) | Blob upload, `PUT /upload`. This is the step that puts the bytes of a picture on a server | Media worth looking at | 🚧 planned | | [Blossom BUD-03](https://github.com/hzrd149/blossom/blob/master/buds/03.md) | User Server List, `kind:10063`: which servers hold your blobs, most trusted first | Media worth looking at | 🚧 planned | | [Blossom BUD-11](https://github.com/hzrd149/blossom/blob/master/buds/11.md) | Authorization for those requests: a signed `kind:24242` event carrying the verb and an expiry | Media worth looking at | 🚧 planned |