{"action":"created","issue":{"url":"https://api.github.com/repos/keybase/keybase-issues/issues/327","repository_url":"https://api.github.com/repos/keybase/keybase-issues","labels_url":"https://api.github.com/repos/keybase/keybase-issues/issues/327/labels{/name}","comments_url":"https://api.github.com/repos/keybase/keybase-issues/issues/327/comments","events_url":"https://api.github.com/repos/keybase/keybase-issues/issues/327/events","html_url":"https://github.com/keybase/keybase-issues/issues/327","id":30037041,"number":327,"title":"Have KeyBase publish itself as a public KeyServer","user":{"login":"EliW","id":1153183,"avatar_url":"https://avatars.githubusercontent.com/u/1153183?v=3","gravatar_id":"","url":"https://api.github.com/users/EliW","html_url":"https://github.com/EliW","followers_url":"https://api.github.com/users/EliW/followers","following_url":"https://api.github.com/users/EliW/following{/other_user}","gists_url":"https://api.github.com/users/EliW/gists{/gist_id}","starred_url":"https://api.github.com/users/EliW/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/EliW/subscriptions","organizations_url":"https://api.github.com/users/EliW/orgs","repos_url":"https://api.github.com/users/EliW/repos","events_url":"https://api.github.com/users/EliW/events{/privacy}","received_events_url":"https://api.github.com/users/EliW/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":113,"created_at":"2014-03-24T14:02:36Z","updated_at":"2016-06-10T23:17:28Z","closed_at":null,"body":"It would be an important step in KeyBase adoption IMO, for it to publish itself as a valid keyserver using the standard protocols for such.\r\n\r\nAs it stands, since keybase doesn't, it means that all the tooling (such as EnigMail for Thunderbird) that has existed for a decade+ ... is unusable against keybase published keys."},"comment":{"url":"https://api.github.com/repos/keybase/keybase-issues/issues/comments/225317798","html_url":"https://github.com/keybase/keybase-issues/issues/327#issuecomment-225317798","issue_url":"https://api.github.com/repos/keybase/keybase-issues/issues/327","id":225317798,"user":{"login":"zQueal","id":239193,"avatar_url":"https://avatars.githubusercontent.com/u/239193?v=3","gravatar_id":"","url":"https://api.github.com/users/zQueal","html_url":"https://github.com/zQueal","followers_url":"https://api.github.com/users/zQueal/followers","following_url":"https://api.github.com/users/zQueal/following{/other_user}","gists_url":"https://api.github.com/users/zQueal/gists{/gist_id}","starred_url":"https://api.github.com/users/zQueal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zQueal/subscriptions","organizations_url":"https://api.github.com/users/zQueal/orgs","repos_url":"https://api.github.com/users/zQueal/repos","events_url":"https://api.github.com/users/zQueal/events{/privacy}","received_events_url":"https://api.github.com/users/zQueal/received_events","type":"User","site_admin":false},"created_at":"2016-06-10T23:17:28Z","updated_at":"2016-06-10T23:17:28Z","body":"I don't work for Keybase. I'm not affiliated with the project at all. I don't speak for them either; so this:\r\n\r\n> With that argument I'd recommend you to stay in beta forever so that you can do with your users whatever you want.\r\n\r\nIs entirely uncalledfor. The only reason why my posts say \"Keybase Member\" is because I'm included in a group which was allowed to beta test the Go client before anyone else (to ensure stability). If I recall I was one of the only users not affiliated with the project which used Windows exclusively.\r\n\r\n> Furthermore, reacting with passive-aggressiveness (explaining how pgp works, seriously?\r\n\r\nI've never met you before in my life. How would I know what type of environment you're working with, or what your level of experience is? For example, I'm running Windows with bash installed, so running that command as an alias would be very simple to implement, but what if you're running Windows without bash? Or maybe you use Keybase on a work computer and can't directly interface with the GPG binary? Wouldn't it be difficult to push a square peg through a round hole? It wasn't meant to be passive aggressive--but if you take it that way, then I guess there's no helping that.\r\n\r\nEveryone has their own views of what is or isn't bullshit, and what is or isn't productive. The only thing I've seen so far is you post your opinion and pass it off as fact. (which isn't cool, man [everything here is my opinion by the way--I'm not trying to pass it off as fact]) Keybase is not GPG. You talk about standards, but GPG pushing keys to a keyserver _is_ a standard and it already does it well. So why would Keybase take the time (which costs money) to make software which already exists? You're asking Keybase to take over for an already existing standard and then hollering when it's not a priority for the developers. Which is _super_ weird considering that Keybase is open source software. If you want it developed so badly, go do it then submit a PR or keep it private for your own usage. You're free to do that instead of calling other people names on the internet...\r\n\r\nIt's not a priority. It probably never will be a priority. Because GPG __already__ does what you want just not the Keybase binary. But so what, just make an alias in the interim...why spend dev time making 100 people happy when they could make 5000 happy with KBFS? The short sighted level of thinking here is.....staggering.\r\n\r\nThe only thing you've successfully done here is derail a pretty productive thread with direct accusations. Which is something open source development could entirely do without; having an opinion is fine, but _expecting_ others to value or respect that opinion simply because you have it? That's quite another thing entirely.\r\n\r\n> This is not about people having difficulties publishing their keys on a keyserver. It is about to get public keys from keybase.\r\n\r\nAs far as I can tell--it's not. Because if it were you're asking for something which already exists __ubiquitously__. There are currently three ways to do it. Not only can you track a user publicly or privately then pull their key directly from Keybase (`keybase pgp pull`) but you can also __directly__ access anyone's public key using this schema:\r\n\r\n    https://keybase.io/{username}/key.asc\r\n\r\nso you don't even need to be using the Keybase software to access public keys and can directly import them using gpg;\r\n\r\n    curl https://keybase.io/{username}/key.asc | gpg --import --\r\n\r\nNot only those two, but you can view the users page on the web interface and just click the fingerprint to view their key in plain text.\r\n\r\n> Hiding behind a beta label is not convincing.\r\n\r\nI really don't want to respond to this because you already seem like the type of person who doesn't listen to others regardless (sorry)--but the software __is__ in beta. No one's hiding behind it. It's __incomplete software__. So you should go forward expecting it to have incomplete features or not work correctly at certain times. This is _expected_ behavior of actively developed software and isn't limited to Keybase or even a tiny handful of software.\r\n\r\nAdditionally, the only thing I've done here is reply to some semblance of an internet troll making me feel like Github comments is now Reddit (which is not a good feeling, by the way and I actually resent you a little for making it feel this way)--and I'm sure no one wants to see two idiots bicker about stupid stuff. (seeing how over 60 people are getting emails for this one stupid conversation--and if you're reading this, I really am sorry) So in the spirit of open development could we __please__ keep the comments civil and constructive? Spilling accusations against bootstrapped developers because they haven't yet implemented a feature you and a bunch of other people want as jerks or unthoughtful towards their users when the _software is still in active development_ is insanely childish and simply not called for.\r\n\r\nLastly, [this is an entirely sane response to this issue](https://github.com/keybase/keybase-issues/issues/327#issuecomment-142680270) and hopefully the direction the Keybase devs go. There's absolutely no reason to reinvent the wheel--especially so when it would only be as good or worse than the current wheel."}}
{"actor":{"display_login":"zQueal"}}