3 ms·
tl;dr - Oh noes, GitHub attempts to make it easy for newbs, and so I can't be smart and do things normally, despite them putting up no barriers to that!
by wccrawford 15y ago
tl;dr - Oh noes, GitHub attempts to make it easy for newbs, and so I can't be smart and do things normally, despite them putting up no barriers to that!
- CJefferson 15y agoYou don't think blindly telling people to move their ssh private key, if it already exists, might lead to newbs breaking their computers? Certainly it would have broken mine if I had done it.
- gks 15y agoOverall I found the blog entry to be lacking any real reasoning why one shouldn't switch or vice-versa. It just feels like a blantant "I want to be on Hacker News" post.
- CJefferson 15y agoThat is I think a sign of bad writing on my part. I certainly didn't write this to be on hacker news, I just wrote it because I was suprised how hard, and possibly dangerous, github's newbie guide is (I have now clarified that I am talking about following github's newbie guide, vs. bitbuckets). I did then submit to hacker news on a whim, first time writing a post, next time I'll sit on a little longer and re-read it later, to make sure I've clearly made my point.
- Kwpolska 15y agoRead the WHOLE guide, then act. It clearly says that you shall not re-create the key if you have one.
- CJefferson 15y agoAre you referring to this line? "Check for SSH keys. Have an existing key pair? You can skip to Step 4" I think many people might not know what that means. Also, why does the next step tell you to move any key pairs you already have, if you are only supposed to do this step if you don't have a key pair? There is a possibility I'm confused, but I think this guide assumes too much, and makes users undertake possibly dangerous changes, when the easier option (login with username/password) is much less risky.