Not sure if I should change the DNN ID encoding to something else than how it's currently done.
Right now we get something like 'nABCeAbsurd' (n-abc-e-absurd), where after ~1.5 years we'd start getting results like 'nABCe1Absurd' (n-abc-e-1-absurd), and the number always increases every ~1.5 years. Also, depending on demand, people might get two words at the end like 'nABCe1AbsurdAbility' (uncommon/rare, but it could happen).
The best alt i can think of, with human readability/memorability in mind, is a result of something like 'nAbilityStealKD' (n-ability-steal-kd), where after around ~80 years we'd start getting results like 'nabilitysteal1kd' (n-ability-steal-1-kdz), the number increases around every 80 years.
nABCeAbsurd (after ~1.5 years a number appears, and increase)
vs
nAbilityStealKD (after ~80 years a number appears, and increase)
(side note: most people would get get 1 or 2 letters at the end most of the time, so nAbilityStealK or nAbilityStealKD, but on high demand it would be nAbilityStealKDO)
(nothing is case-sensitive btw)
After asking two famility members (normies) on which would they most likely remember, easily read and share, write, out of the two following options:
nABCeAbsurd
nAbilityStealKD
They chose the second option.
So I'll most likely change it to that.
Keep in mind that this is an ID, a TLD (google.nabilitystealkdo), and part of a short link of posts with nip-short (.com/post/e-nabilitystealkdo-3qgx-f515d).
Asking here a well, which type would you prefer and remember?
nABCeAbsurd
(worst result within 200 years: nABCe123AbsurdAbility)
nAbilityStealKD
(worst result within 200 years: nAbilitySteal2KDO)
Freakoverse
npub18n…zzk9r
2026-02-07 12:27:42 UTC
Author Public Key
npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9rSeen on
wss://relay.degmods.comPublished at
2026-02-07 12:27:42 UTCEvent JSON
{
"id": "19c6d9b8ae13d3d54a51c563096e6df914b594598652690d2e566fca3b3c8492",
"pubkey": "3cea4806b1e1a9829d30d5cb8a78011d4271c6474eb31531ec91f28110fe3f40",
"created_at": 1770467262,
"kind": 1,
"tags": [],
"content": "Not sure if I should change the DNN ID encoding to something else than how it's currently done.\n\nRight now we get something like 'nABCeAbsurd' (n-abc-e-absurd), where after ~1.5 years we'd start getting results like 'nABCe1Absurd' (n-abc-e-1-absurd), and the number always increases every ~1.5 years. Also, depending on demand, people might get two words at the end like 'nABCe1AbsurdAbility' (uncommon/rare, but it could happen).\n\nThe best alt i can think of, with human readability/memorability in mind, is a result of something like 'nAbilityStealKD' (n-ability-steal-kd), where after around ~80 years we'd start getting results like 'nabilitysteal1kd' (n-ability-steal-1-kdz), the number increases around every 80 years.\n\nnABCeAbsurd (after ~1.5 years a number appears, and increase)\nvs\nnAbilityStealKD (after ~80 years a number appears, and increase)\n\n(side note: most people would get get 1 or 2 letters at the end most of the time, so nAbilityStealK or nAbilityStealKD, but on high demand it would be nAbilityStealKDO)\n\n(nothing is case-sensitive btw)\n\nAfter asking two famility members (normies) on which would they most likely remember, easily read and share, write, out of the two following options:\nnABCeAbsurd\nnAbilityStealKD\n\nThey chose the second option.\n\nSo I'll most likely change it to that.\nKeep in mind that this is an ID, a TLD (google.nabilitystealkdo), and part of a short link of posts with nip-short (.com/post/e-nabilitystealkdo-3qgx-f515d).\n\nAsking here a well, which type would you prefer and remember?\nnABCeAbsurd\n(worst result within 200 years: nABCe123AbsurdAbility)\nnAbilityStealKD\n(worst result within 200 years: nAbilitySteal2KDO)",
"sig": "4452efda3707d2038aefac9798b2e222cce844bd4edd5c1f330b17e15059cb0caec59dd7e1c9610147e1c8142d7bbeb7d36762257cab2341aedbd886ba35fa0b"
}