@michael yeah we tried making it standard but no luck.
As for the CLI, JS is indeed not an optimal choice but they're all stepping stones. When you're not a multimillion company, you need a few more of those.
Though at this moment not my highest priority, the CLI will also be rewritten, likely in rust
Hi 👋! I’ve designed the original email@example.com notation.
Sorry for the inconvenience! As you’ve found out Keyoxide uses that for backwards-compatibility reasons.
The story goes like this: the original used my domain name because that’s what RFC 4880 requires for non-standardized notations. Then Keyoxide begun to use it, and keys.openpgp.org also had profiles at some point: https://gitlab.com/hagrid-keyserver/hagrid/-/merge_requests/172
The domain part was always problematic, everyone wanted their own domain in there (gee, I really need to update the homepage :-/ ) 🤷 and I thought it would be better to get the name in IANA namespace. Unfortunately it didn’t go well, it seems my proposal lacked a couple of people that'd express they would want the proof notation in the spec and so that just didn’t happen.
Using standardized notation would also mean users would have to pass --expert flag to GnuPG when adding notation (minor inconvenience). Seeing you’re not the first (and last) person not to like my domain name I guess the migration to @keyoxide.org is imminent. (Well, people think of these proofs as “keyoxide proofs” now anyway).
Hope this clears some matters up. Sorry for the confusion again!
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!