4 ms·
Don't know why people would downvote this. The permission this site is asking is only email address associated with Github. As someone who is always logged in w
by octref 11y ago
Don't know why people would downvote this. The permission this site is asking is only email address associated with Github. As someone who is always logged in with Github, this saves me from creating another account associated with my email address.
- sdoering 11y agoWell this could be done without having me entered into a public leaderboard and having some kind of "who's is bigger" contest made out of it. I very much would prefer the content to be accessible without this ego-bolstering crap. Sorry, but local storage or a cookie dropped would suffice. Why should this introduction be in any way tied to me or my Github profile? It may be so easy, to just log in with Github. But for me this just kills it. I assume, that a lot of people think alike - that might be the reasons for downvotes.
- Ntrails 11y agoI don't even have a github account (unheard of on HN I know), so the requirement to create one to use the site essentially means it goes in the bin.
- jononomo 11y agoOr you could just create a github account...
- lectrick 11y agoGiven the number of other sites that work with Github authentication, it seems silly to me to not want to save some effort and... just sign up for Github Disclaimer: I'm pro-Github... well, other than the fact that it's centralizing a decentralized SCM. ;)
- octref 11y agoInteresting how you consider it ego-bolstering. Can't you just ignore the leaderboard? It seems a lot of effort goes into making this tutorial. The guy working on it seems to be running a business. Although it can be done without requiring a sign-up as you said, I also understand how the author would like more people to sign-up, follow the competition, and potentially use his company's service. Writing good tutorial is actually pretty hard and time-consuming. Just making it open and not getting any benefit out of it is not a sustainble business.
- jononomo 11y agoWell said.
- sdoering 11y agoWell I could ignore it, if it were not tied for ever to my github account. Something some future employer might have a look into. And maybe I suck at this thing and... ... well you get the point. If I want to have it on my resume, I will put it there. If not it should not be findable, because I once looked into it, but maybe didn't have the stamina to push through. So maybe "ego-bolstering" was a bit harsh. But non the less - this requirement just killed it.