why-el

32 ms·

301.
by why-el 11y ago
As long as they get a vendor zone, that is. LP is against this, since he does not consider systemd to be a vendor.
302.
by why-el 11y ago
Yep, even from an SEO standpoint this is not a very good title to have indexed by robots.
303.
by why-el 11y ago
What a terrible thing to say. The guy also did his bachelor's here, has friends here, and lived enough to consider this place his home.
304.
by why-el 11y ago
I second this recommendation. "Code" is a very enjoyable read indeed.
305.
by why-el 11y ago
Only one reviewer is enough for us. Once a PR is submitted to GitHub, it should be merged by the reviewer, who usually only has to click that GitHub merge button. This means we favor a rebase-workflow, which has worked great for us. There a
306.
by why-el 11y ago
Things get upvoted for a lot of reasons, chief of which is getting tips from people who use the same tool, like the comment that tops the list right now.
307.
by why-el 11y ago
I guess you are not using "Wait! Google Sent Me" chrome extension? (assuming you are using chrome)
308.
by why-el 11y ago
Not as much Java as the JVM, because even if people are abandoning Java the language, the JVM will survive I think since not-insignificant languages such as Clojure and Scala are using it. Learning Java to a comfortable degree will most lik
309.
by why-el 11y ago
A little meta, but it's a good decision that Github has separated their technical blog posts from the rest (previously they used to combine all posts in github.com/blog). This was much needed given the nature of their customers.
310.
by why-el 11y ago
You do realize this is in nowhere pretending to be near as effective as a novel written even by the most okayish of writers right?
311.
by why-el 11y ago
Oh wow, this is very cool.
312.
by why-el 11y ago
I was completely aware of the issue and I chose specifically to let it happen (As was very clear from the README). This is an exercise in how the community can bend the nature of Git to serve a nice purpose. Absolutely no issues if this fai
313.
by why-el 11y ago
Hello HN, this is the author. The repo needs structure and some organization, which I specifically said I forwent during my initial launch as an experiment to see what structure will emerge by simple PR merging, and if too many git conflict
314.
by why-el 11y ago
What would be your suggestion to improve it?
315.
by why-el 11y ago
Timeframe, I have no idea. For merging, I'd go with consensus unless it starts to bikeshed, then I'll BDFL it.
316.
Let's Crowd-Write a GitHub Novel(github.com)
47 points by why-el 11y ago|44 comments
317.
by why-el 12y ago
I am slightly confused. How can they have use their "hash map of popular passwords" to diff against your table if they do not have the "pepper" used originally for bcrypting the passwords?
318.
by why-el 12y ago
Thank you. :)
319.
by why-el 12y ago
> Some effort must be put into supporting TCP/IP Stacks in Userspace using new 10GBe cards or support for IB verbs Obviously my understanding of networks is not at that level yet. What would a layman do to become somewhat vested in
320.
by why-el 12y ago
Which one of those (w3m, dillo, netsurf) is your favorite? And how do you deal with privacy in the absence of addons such as Ghostry, adblock, and so on?
321.
by why-el 12y ago
Good points from Chris, but of course this depends on where one is. Growing up in a country that has shocking levels of illiteracy, I assure you that being literate, even in its most basic form, is already a tremendous step forward. If you
322.
by why-el 12y ago
This one should be the default if you ask me.
323.
by why-el 12y ago
Spotify has had a wonderful and simple UX for a long time, but after their US opening they did some bizzare changes that made it look very bloated. I reckoned this happened after Rasmus Andersson left them for Facebook. He seemed the one wi
324.
by why-el 12y ago
I think you can repost about a year. It could have changed tough.
325.
NASA will pay you to stay in bed(businessinsider.com)
2 points by why-el 12y ago|0 comments
326.
by why-el 12y ago
Is there any published research on this? I am interested to learn about these risk analysis techniques they are talking about.
327.
by why-el 12y ago
I mentioned exactly those what I think "some way to narrow it down" is, mainly new websites with significantly less users, websites where its common to have your username known in public, and even websites that allow you to query
328.
by why-el 12y ago
Perhaps misleading was the wrong word, but as you said it yourself, saying that would lead to a user experience that is much worse than a simple "Bad experience", which is exactly my point.
329.
by why-el 12y ago
None of the author's recommendations conflict with the practice he is advocating against. I think websites say "Bad combination" not because usernames are treated equally with passwords, but because you don't have a choi
330.
by why-el 12y ago
Then I think you will enjoy this thread. :) http://stackoverflow.com/questions/184618/what-is-the-best-c...

More ›