kuiperbelt on Nostr: NIP-52 events have t and g tags. But when I do a REQ like this: [REQ, "subid", ...
NIP-52 events have t and g tags. But when I do a REQ like this:
[REQ, "subid", {"#t":["hashtagtest"]}]
Then the relay accepts my request but shows no responses.
However, if I put this in my filter:
[REQ, "subid", {"ids":["idofcalendarevent"],"#t":["hashtagtest"]}]
then it finds my event. I believe these two filters should be && because they're in the same JSON object. BUT what I think is happening is that the "#t" bit is being ignored by the relay.
Is this a bug in the relay I'm using?
#asknostr #dev
Published at
2024-04-18 16:27:55Event JSON
{
"id": "c75638730e340a65bced4bd476639d495c104269afef1ad58a4be93e4a3fb6f7",
"pubkey": "1d7792404ebfae1ce89cedf939ea2a2954ae58997bf084f96ed312f965359001",
"created_at": 1713457675,
"kind": 1,
"tags": [
[
"t",
"asknostr"
],
[
"t",
"asknostr"
],
[
"t",
"dev"
],
[
"t",
"dev"
]
],
"content": "NIP-52 events have t and g tags. But when I do a REQ like this:\n\n[REQ, \"subid\", {\"#t\":[\"hashtagtest\"]}]\n\nThen the relay accepts my request but shows no responses.\n\nHowever, if I put this in my filter:\n\n[REQ, \"subid\", {\"ids\":[\"idofcalendarevent\"],\"#t\":[\"hashtagtest\"]}]\n\nthen it finds my event. I believe these two filters should be \u0026\u0026 because they're in the same JSON object. BUT what I think is happening is that the \"#t\" bit is being ignored by the relay.\n\nIs this a bug in the relay I'm using?\n\n\n#asknostr #dev",
"sig": "4ca67d246299b64a732bb7ffc8f23a941f408f25cf201f465dc41242f692a900111419436486516ebc7a1d851399884fc8d4055c9ab09c1e29d4a7ab7917e808"
}