mleku on Nostr: when there is a repository storing data for you, you can have cross-installation ...
when there is a repository storing data for you, you can have cross-installation state, what's the argument against using this part of the relay architecture? redundancy already easy to add just by storing it on other relays, it's encrypted to your own secret so it's not able to be breached by cryptanalysis, and the metadata is mostly worthless except to catch your activity cycle perhaps, and with auth those events can be restricted from non-privileged access and with cache management, a history and a limit on the number of historical versions
Published at
2024-07-03 11:56:28Event JSON
{
"id": "83d686fe9e08db0c9ec250abf72288354011a1dc3c1fb083f5a110f2c14fffbe",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1720000588,
"kind": 1,
"tags": [
[
"e",
"49f673e7f4e383e054ab96280041560b088879406f72a1910ccb1ff58d2ded2e",
"wss://relay.primal.net/",
"root"
],
[
"e",
"db1cdf6e49fde8f53e21d0f30e6f4639a02d851c49a39d7f39e3a502b5ff6edd",
"",
"reply"
],
[
"p",
"1739d937dc8c0c7370aa27585938c119e25c41f6c441a5d34c6d38503e3136ef",
"",
"mention"
]
],
"content": "when there is a repository storing data for you, you can have cross-installation state, what's the argument against using this part of the relay architecture? redundancy already easy to add just by storing it on other relays, it's encrypted to your own secret so it's not able to be breached by cryptanalysis, and the metadata is mostly worthless except to catch your activity cycle perhaps, and with auth those events can be restricted from non-privileged access and with cache management, a history and a limit on the number of historical versions",
"sig": "16509bb331f3e20f99f37745e8f21066d33ce1a508d7295e823099a566d0c33f615ab21c877163b5a4e80b5092607e05545c0ef4577fc820f06d20c6cecd1e3f"
}
