wakoinc on Nostr: NostrGraph 7 day reactions (less than 4 chars). For databases, reactions are actually ...
NostrGraph 7 day reactions (less than 4 chars).
For databases, reactions are actually not amazing. For a single character (ignore UTF8), it’s basically 500 characters in event JSON.
You can certainly extract the reaction, and even use something like hyperloglog to compress that way down - and even using the reaction event creator local DB id, and then you can delete the reaction, but avoid double counting too. However, you then can’t broadcast, search or prove that reaction after deletion. Maybe that doesn’t matter.
We’ll either get better at handling data and processing for stuff like this, or it will have to change anyway, as relays won’t be able to host all the data in its current form - even for a 30 day period.
Published at
2023-04-21 17:07:23Event JSON
{
"id": "9798c995a36c251f584e9395596db25b3082c4beb719106dd63f358584c2df1f",
"pubkey": "b2dd40097e4d04b1a56fb3b65fc1d1aaf2929ad30fd842c74d68b9908744495b",
"created_at": 1682096843,
"kind": 1,
"tags": [],
"content": "NostrGraph 7 day reactions (less than 4 chars). \n\nFor databases, reactions are actually not amazing. For a single character (ignore UTF8), it’s basically 500 characters in event JSON. \n\nYou can certainly extract the reaction, and even use something like hyperloglog to compress that way down - and even using the reaction event creator local DB id, and then you can delete the reaction, but avoid double counting too. However, you then can’t broadcast, search or prove that reaction after deletion. Maybe that doesn’t matter. \n\nWe’ll either get better at handling data and processing for stuff like this, or it will have to change anyway, as relays won’t be able to host all the data in its current form - even for a 30 day period. \n\nhttps://i.ibb.co/3Tg5FMF/image.png ",
"sig": "996b5f37a238a419a795933d2ac3ad9c4eafba2774a6cfd9522ed697a8d18a587817888e6f874cf80407e1b3344d9a63caabf61958484df8e5ce77c835872c32"
}