Event JSON
{
"id": "13677261c60bc94795638ef4e713f462b24ed71c2890caef82246727d272cf63",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1737972084,
"kind": 1,
"tags": [
[
"e",
"163bbfda603d3dbbeca1e8aaf447ba4e42eea324a3bc4cae25e80e6500150be9",
"",
"root"
],
[
"e",
"abfff7609544bdf9dd421b785ac3dbc4900fbb047f69235f161c3995be4282f9",
"nostr-idb://cache-relay",
"reply",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
],
[
"p",
"52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd"
],
[
"p",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "my biggest problem with nip-29 apart from its excessive complexity is the fact that it doesn't lend itself to scaling to join multiple small relays to provide redundancy, this is why in my proposed nip-79 \"nostr relay chat\" one of the first things it attends to is how to wrap messages so they can be broadcast across to other members of a relay group\n\nhttps://github.com/mleku/nips/blob/master/79.md\n\nnip-29, as nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj is pointing out, binds the messages to only be valid and this has problems with DNS being then also tied to it\n\nnip-79 makes no prescriptions about relays storing the data, it's my intention that clients like the IRC model of chanserv will cache messages and deliver them to users to enable async messaging",
"sig": "34b5dde762da2edc01f674bbd9ce90099fb68eb28f5ce3258224dfe3555df7a0c6728e1b2373e0beee523eaaec0580cc5a05278e188a2bd86d219837146fe63e"
}