mleku on Nostr: in bluesky they use a "root" and "reply" pair for structuring thread trees, i think ...
in bluesky they use a "root" and "reply" pair for structuring thread trees, i think in nostr there is exactly this as the third parameter of `e` tags
this thing about mentions is stupid, who proposed that in the first place? at best, IMO the reply's parent (to which the "reply" marked `e` tag points should implicitly be notified and there should be no explicit need for the use of mention tags that are implicitly generated like this
Published at
2024-11-18 14:55:43Event JSON
{
"id": "72620fca1df8522b71926851d5c958d8baabb2399d6789333f8826eadf93b2b2",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1731941743,
"kind": 1,
"tags": [
[
"e",
"6a6af001fa6c4437e2f66ebd225cae972bce18d4f22848f890a08274c4c4067c",
"wss://nostr.roundrockbitcoiners.com/",
"root"
],
[
"e",
"8fca040b3fb05b9483a00b356dbca92f1eb023f3d3131e0d72c69439b87e4913",
"wss://relay.nostr.band/",
"reply"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"",
"mention"
],
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "in bluesky they use a \"root\" and \"reply\" pair for structuring thread trees, i think in nostr there is exactly this as the third parameter of `e` tags\n\nthis thing about mentions is stupid, who proposed that in the first place? at best, IMO the reply's parent (to which the \"reply\" marked `e` tag points should implicitly be notified and there should be no explicit need for the use of mention tags that are implicitly generated like this",
"sig": "aee41d27c16bd58f61dcf3a9861269e1b82c0d9427eeb14ba5d622105af07a2e5c7945ee7cbb6d91d115454f96f62942fdf750a1be99db790b12377475c42fc2"
}
