I got you covered. My take on it:
@sheogorath Wow, thanks, I was just looking for this
@sheogorath I've set it up. Do you know anything about adding Access-Control-Allow-Origin header? I've tested it here but not getting positive test for that header in nginx config
@nikolal For which nginx config?
@sheogorath Found it, I was missing header for .well-known/openpgp/hu. Thanks
Yep, I just did a small fix to the lookup page and now it does WKD if an e-mail is passed: https://firstname.lastname@example.org or https://email@example.com
The keyserver is used only when looking up via fingerprint. (btw if you don’t know https://keys.openpgp.org/ is a new generation keyserver, this is not what you expected from SKS).
@nikolal kind of a GPG problem overall, at least it works with the new keyservers.
@rysiek @jonah @wiktor @nwalfield I suppose if a thing is useful to do, then it's worth doing it in a decentralized way. So yay for wiktor working on this! (Personally, I haven't wanted to do "social proofs" so far, but I'm a grumpy person who'd rather not link every one of my things to every other one of my things - not even without using cryptography).
To be honest I’m also not a big fan of social proofs. It just annoyed me that Keybase made something centralized with no clear reason so I made it decentralized following the design of Vincent (https://chaos.social/@Valodim).
Consider this a weekend project with one reason: because it *can* be done! ;)
Ha, you really did set it up: https://metacode.biz/openpgp/key#0x6A957C9A9A9429F7
Cool! Do you mind if I use your key as a reference in the docs on how it works? I used mine but then it looks just weird :)
@wiktor not sure why I didn’t get a notification for this reply but sure, if you still want to 😅
@jonah You might be interested in this: