it's based on two things about how tags and filters work
1. single letter tags are indexed so finding them is fast and selective
2. the match on the second field (all elements after [ "#x", "<value>", ... ] are prefix matches, whatever your <value> is, it matches if the candidate event tag has that same prefix.
i don't know if that is explicitly stated in the NIP-01 spec but that's how fiatjaf implemented it in Go for go-nostr.
so, yes, it enables precisely this kind of thing, where you have general -> specific segments of the tag string. Tag strings are limited to 100 characters but that is plenty for concise multi-segment values.
mleku
npub1fj…mleku
2025-03-30 08:31:25
in reply to nevent1q…fnqp
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuSeen on
wss://nostr.winewss://theforest.nostr1.comwss://lnbits.papersats.io/nostrclient/api/v1/relaywss://relay.damus.ioPublished at
2025-03-30 08:31:25Event JSON
{
"id": "be031550b69cb32d616bf5a49db46caa49d22324ba0392f79be7d497f4e4cedf",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1743323485,
"kind": 1,
"tags": [
[
"t",
"x"
],
[
"e",
"2fce773d43cd47c008aee0728e626cd0a6f99aa097f36d079bb94903fb340aa3",
"",
"root",
"6e468422dfb74a5738702a8823b9b28168abab8655faacb6853cd0ee15deee93"
],
[
"e",
"95f967ec5b908f24e868319ffb20333511554c44de3a921c425b5a0d11d80712",
"wss://theforest.nostr1.com/",
"reply",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"p",
"6e468422dfb74a5738702a8823b9b28168abab8655faacb6853cd0ee15deee93"
],
[
"p",
"592295cf2b09a7f9555f43adb734cbee8a84ee892ed3f9336e6a09b6413a0db9"
],
[
"p",
"b90c3cb71d66343e01104d5c9adf7db05d36653b17601ff9b2eebaa81be67823"
],
[
"p",
"7fa56f5d6962ab1e3cd424e758c3002b8665f7b0d8dcee9fe9e288d7751ac194"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
],
[
"p",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"client",
"jumble"
]
],
"content": "it's based on two things about how tags and filters work\n\n1. single letter tags are indexed so finding them is fast and selective\n\n2. the match on the second field (all elements after [ \"#x\", \"\u003cvalue\u003e\", ... ] are prefix matches, whatever your \u003cvalue\u003e is, it matches if the candidate event tag has that same prefix.\n\ni don't know if that is explicitly stated in the NIP-01 spec but that's how fiatjaf implemented it in Go for go-nostr.\n\nso, yes, it enables precisely this kind of thing, where you have general -\u003e specific segments of the tag string. Tag strings are limited to 100 characters but that is plenty for concise multi-segment values.",
"sig": "c3e67078f98ab912186dd0a81ee95054daf7ed66892cd0ae13688364f0ed559b649ec26f5657e8698ea09d3be219bd7e490586da2cb7e77019c7c477defc6ef1"
}