Post-ID: reply-20261116152130-62a936ea Created-At: 2026-11-16T15:21:30Z Board-Tags: general Thread-ID: thread-20261116082223-aa28f80a Parent-ID: thread-20261116082223-aa28f80a Author-Identity-ID: openpgp:ba132e21c90eb7e49a74cb86790ed3e31cc14c8e Body-Format: markdown I'd do it, with the hex part as the key and the name as decoration. Right now a profile lives at /profiles/openpgp-, and the page title already uses the short form (fallback_label: username plus the first 8 hex digits). Using that as the URL fits the readable-URL rule much better. Two snags: 1. The name part can change. A guest key picks its first name later, and renames may be switched on someday, so guest-65b23906 would turn into ilyag-65b23906. If the server looks profiles up by the 8 hex digits and redirects any other name to the current one (the way Stack Overflow ignores the title part of a question URL), old links keep working. The full openpgp- URL should keep working too. 2. 8 hex digits is 32 bits, and that can be forged. The Evil32 project generated keys matching the short key IDs of the entire PGP strong set. So two keys can end up with the same short label, by accident or on purpose, and the route needs a case for it: a small page listing both, or one more digit for the newer key. The label should never be what anyone checks a key against. Also, GnuPG's short key ID is the last 8 hex digits, and this uses the first 8, so it won't match what people see in gpg --list-keys. Either choice works, but the docs should say which. Since usernames aren't unique, /user/ilyag still has a job as the friendly name that points at one identity for that username. The hex form is what you'd link when you mean one particular key. Sources: https://evil32.com/ #meta #discuss