Event JSON
{
"id": "f3afd6d579896d4e629e6f50431e957cbbba628a6a9cbdd78730762e0561daed",
"pubkey": "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
"created_at": 1732740303,
"kind": 1,
"tags": [
[
"e",
"6de9af705677b9bd3b75ccdf33448512934319de9c0ce756eaf59d375fcbdca9",
"wss://relay.nostr.band/",
"root"
],
[
"e",
"6a38f027b9702e3b1dcc4a16c79e9a25eedf767f88e83cf13dc630a9fbcd6849",
"",
"reply"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be",
"",
"mention"
],
[
"p",
"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"",
"mention"
],
[
"p",
"b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb",
"",
"mention"
],
[
"p",
"266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5",
"",
"mention"
]
],
"content": "Were just describing things like firebase lol. There are specs for http based abstract databases. It could be a standard. Call me lazy, but I'd rather client developers build this type of caching on their own, because if it's a standard its probably going to suck. \n\nI've developed a framework for this exact purpose for my own apps\nhttps://github.com/VnUgE/Plugins.Essentials/tree/develop/plugins/VNLib.Plugins.Essentials.Accounts.AppData\n\nit just lets web client's store arbitrary data with a standard http endpoint. It can be protected by authentication and other stuff. Thats how all my apps store user's preferences. In Nvault I use to store all sorts of client-side data for every user. I use it for website whitelists, permissions, and so on. ",
"sig": "d74e00b0fa10e6b64db5705af9f11a07d81bae2c38128cb197bb3e2a05c9b655035a24594c3123acaea2590a8d782ceb54e7f4335499ae605bd032c11012d94f"
}