Event JSON
{
"id": "7fcdcc0b8c39cc82c25934799a9512ae14d24764e252fa3398b34e8dfefda6d7",
"pubkey": "70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9",
"created_at": 1720452660,
"kind": 1,
"tags": [
[
"p",
"70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9",
"",
"mention"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
"wss://140.f7z.io/",
"mention"
],
[
"p",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"p",
"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"",
"mention"
],
[
"e",
"265f615b4bdf3eef9c4a550430dc08d30510ba049870e6646bab3df0fbfb36c1",
"wss://relay.wellorder.net",
"root"
],
[
"e",
"edfff015933ba1b83174ddcaf89f99a401ab98a05d8a9c9506df29d6cea8231a",
"wss://theforest.nostr1.com",
"reply"
],
[
"t",
"asknostr"
],
[
"t",
"nostrdev"
]
],
"content": "Maybe we can use additional d tag fields for structured identifiers, sort of like nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku has been talking about.\n\nSo you could have `[ \"d\", \"1-john\", \"rsv\" ]` and `[ \"d\", \"1-john\", \"kjv\" ]` to identify two separate events (for different translations) by the same npub.\n\n#asknostr #nostrdev how do clients/relays typically handle d tags with multiple identifiers, if at all?",
"sig": "3efee5ed08d2770e4eb20bf67ece097fa2c2792ba947bf33ac5930c848387dbd08d4b906d241e6a5f81b6738253b7ac04c167f027ed1b74af057aebe542db520"
}