3 ms·
>Keybase has a pretty good command line tool Another example of the walled garden. You need their tool, whereas you can just use gpg with every other keyserve
by davexunit 10y ago
>Keybase has a pretty good command line tool
Another example of the walled garden. You need their tool, whereas you can just use gpg with every other keyserver.
- WorldMaker 10y agoSure. It would be great if they supported both. The suggestion is to use their tooling because it provides a lot of added value, but yes, it would be great if they also provided a standard "dumb" PGP/GPG keyserver, too. Maybe consider contributing to the effort? Quick searched turned up several issues tracking the question: https://github.com/keybase/keybase-issues/issues/327 https://github.com/keybase/keybase-issues/issues/327 https://github.com/keybase/keybase-issues/issues/890 https://github.com/keybase/keybase-issues/issues/890 https://github.com/keybase/keybase-issues/issues/1266 https://github.com/keybase/keybase-issues/issues/1266
- davexunit 10y agoI'm not interested in giving free labor to a for-profit company whose server source code is proprietary.
- WorldMaker 10y agoI get it. I mostly just meant contributing extra emojis to the issue tracker. Or if you read the issues you can see that there are some genuine concerns in there that you could help contribute to that would benefit the open source community as a whole, with the side effect of simplifying things for Keybase "as well". Primarily, from skimming, it sounds like the keyserver protocols are not as well documented and standardized as one would assume, running a keyserver from a fresh/new code base is a non-trivial matter with a lot of quirks/bugs to handle. So, who knows, maybe you could contribute to better documenting keyserver quirks, and pushing for better, less quirky, keyserver standards.