LOL! Note IDs, nevents, naddrs, and hex IDs... So many to try and keep straight!
I think I've got it now, though. So you are proposing making a mnemonic phrase out of the first 6-8 characters of the HEX ID of, well, anything you want to, right? Could be the hex version of a user's npub, the hex version of a bookmark list's ID, or the hex version of a book ID published to Alexandria, and as long as the Nostr client knows where to look for it, since relay hints aren't encoded into the hex, only the nevent or naddr, the client should be able to find it with just that mnemonic phrase.
And hex IDs are completely different from nevents and such. You can't just take the "nevent" prefix off of the front and what you are left with is the hex ID. It's a completely different set of characters.
Jumble is kind enough to allow users to see the raw event information if they want to, and I believe the hex ID of your reply is:
`a50bc29d3377e1b0f50a0f471ca7431d27489f013df620a90e313c5f10b1c2a9`
While the nevent is:
`nevent1qvzqqqqqqypzp68dx7vvdlltl7sg2qdv8838ze3tl5tq76y0jnz966fdsana6dz6qyt8wumn8ghj7mn0wd68yetvd96x2uewdaexwtcpr9mhxue69uhhwmm59e38y6t8dp6xymmvwshxuet59uqzpfgtc2wnxalpkr6s5r68rjn5x8f8fz0sz00kyz5suvfutugtrs4ffsug0m`
But we could have clients display an option to copy an "event seed" or some similar title for it, which is a mnemonic phrase of human readable words that represent the first 6-8 characters of the hex ID.
So, the question becomes, how will clients know where to find the referenced event without relay hints?
Do we have "indexer" relays that just record hex IDs and what relays they were seen on, so clients can reach out to the indexer to tell them where to look for the event? Or do we use a DHT for that? Or do we make the phrase 12 words, with the first 6 being a mnemonic of the author's pubkey and the last 6 the mnemonic of the event, and then the client can just check the author's kind 10002 relay list to see where to look for the event?
Dikaios1517
npub1ku…v3lhe
2025-05-08 15:28:04
in reply to nevent1q…utzx
Author Public Key
npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhePublished at
2025-05-08 15:28:04Event JSON
{
"id": "70257273e66becfa06c59ce20a1016b1690fde648008a5ce10295dd32588cfe2",
"pubkey": "b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb",
"created_at": 1746718084,
"kind": 1,
"tags": [
[
"e",
"ac63b28f8b6fdadebb84e5375910d7cdce711e81b5ed9f6fce4e33f451c421ad",
"",
"root",
"2efaa715bbb46dd5be6b7da8d7700266d11674b913b8178addb5c2e63d987331"
],
[
"e",
"a50bc29d3377e1b0f50a0f471ca7431d27489f013df620a90e313c5f10b1c2a9",
"wss://nostrelites.org/",
"reply",
"e8ed3798c6ffebffa08501ac39e271662bfd160f688f94c45d692d8767dd345a"
],
[
"p",
"2efaa715bbb46dd5be6b7da8d7700266d11674b913b8178addb5c2e63d987331"
],
[
"p",
"16d76f262b689bb1a33faa2df954dbe7ac717937fad4765a05ddfae3dac92856"
],
[
"p",
"e8ed3798c6ffebffa08501ac39e271662bfd160f688f94c45d692d8767dd345a"
]
],
"content": "LOL! Note IDs, nevents, naddrs, and hex IDs... So many to try and keep straight!\n\nI think I've got it now, though. So you are proposing making a mnemonic phrase out of the first 6-8 characters of the HEX ID of, well, anything you want to, right? Could be the hex version of a user's npub, the hex version of a bookmark list's ID, or the hex version of a book ID published to Alexandria, and as long as the Nostr client knows where to look for it, since relay hints aren't encoded into the hex, only the nevent or naddr, the client should be able to find it with just that mnemonic phrase.\n\nAnd hex IDs are completely different from nevents and such. You can't just take the \"nevent\" prefix off of the front and what you are left with is the hex ID. It's a completely different set of characters.\n\nJumble is kind enough to allow users to see the raw event information if they want to, and I believe the hex ID of your reply is:\n\n`a50bc29d3377e1b0f50a0f471ca7431d27489f013df620a90e313c5f10b1c2a9` \n\nWhile the nevent is:\n\n`nevent1qvzqqqqqqypzp68dx7vvdlltl7sg2qdv8838ze3tl5tq76y0jnz966fdsana6dz6qyt8wumn8ghj7mn0wd68yetvd96x2uewdaexwtcpr9mhxue69uhhwmm59e38y6t8dp6xymmvwshxuet59uqzpfgtc2wnxalpkr6s5r68rjn5x8f8fz0sz00kyz5suvfutugtrs4ffsug0m`\n\nBut we could have clients display an option to copy an \"event seed\" or some similar title for it, which is a mnemonic phrase of human readable words that represent the first 6-8 characters of the hex ID.\n\nSo, the question becomes, how will clients know where to find the referenced event without relay hints?\n\nDo we have \"indexer\" relays that just record hex IDs and what relays they were seen on, so clients can reach out to the indexer to tell them where to look for the event? Or do we use a DHT for that? Or do we make the phrase 12 words, with the first 6 being a mnemonic of the author's pubkey and the last 6 the mnemonic of the event, and then the client can just check the author's kind 10002 relay list to see where to look for the event?",
"sig": "5b2a33cccc1e4bd2777fd35d8973d5d67aa033f9e6eaabf89501bd6e3a7e022ad34f3433d84021c60f44922051633243f6cbb8483c9ec11b9bd2d2b77cec1280"
}