AdemanTemp on Nostr: Managing collisions in numeric ids is going to suck though if people start really ...
Managing collisions in numeric ids is going to suck though if people start really developing new use cases. At least with named event types you have to be working on something similar to collide. It's at least debatable.
Encoding persistence properties into the number ranges was a horrible idea though.
Published at
2023-02-28 17:41:31Event JSON
{
"id": "1d80116a593b293cd12aa9f43da6581e960e7597ac66fec7482951adcf72f4c2",
"pubkey": "c1d49e66dd4c34950e994a8673537aeff5ea8fdad7d19e61c0f21008487db4c4",
"created_at": 1677606091,
"kind": 1,
"tags": [
[
"e",
"5e0cec14ba8cea1fa52f03279201a69924b67997afcf9e369515182942b62be8",
"",
"root"
],
[
"p",
"a06f17ffb19bf45857e5974ac8bb1bea578189786eea458e443bdf8c3d533bd3",
"wss://relay.mostr.pub"
]
],
"content": "Managing collisions in numeric ids is going to suck though if people start really developing new use cases. At least with named event types you have to be working on something similar to collide. It's at least debatable.\n\nEncoding persistence properties into the number ranges was a horrible idea though.",
"sig": "efc757c3c4fb579606b4ae59209dc688dec3f2e1a9e4b28f733183008e04f5137ce7caf02532319c6263e244171d5d6bdb10b29f26ca3e4bad517ea12f2e176a"
}
