883 karma · joined April 10, 2013
I don't have strong opinions on OAuth or any other federated identity solution, I just think it's a specious claim to say that just because a system doesn't care about who a user is then that system doesn't care about the uniqueness of that user.
I may not care who they are, but I do care how their identity maps to information in my system. Simple functionality such as favorites or saved preferences doesn't require any information about the user, other than them being able to identify themselves as someone who has previously used the site.
From looking at their tests and the PowerPoint file in their repo, they mention confirming that the hostname provided by the server in the challenge matches the SSL Certificate. Asking as someone who knows very little about crypto, under the assumption that they validate the hostname and are using TLS would it still be vulnerable to a replay attack?
I don't think it's saying that storing the hash is bad, it's saying that sending an unmodified password to be hashed on the server is bad since that server now has your cleartext password.
http://www.amazon.com/dp/B008U6V50U
It's smooth as butter, and there are no stickers to cheat with.
I commonly try to get Google Maps directions as I leave the house, and often it just fails since it's still trying to use my WiFi which is too far away to be useful.
If you haven't read Dune, go pick it up. It's a great piece of science fiction with a mythical element like the article describes.
You can have the best of both worlds. For example, I use Visual Studio with the VsVim plugin. Visual Studio is my IDE, but vim is my editor.
http://webcache.googleusercontent.com/search?q=cache:SmNdAIe...
console.mihai()
> "http://incompleteness.me/blog/2015/02/09/console-dot-mihai/" /* Use responsive pixels */
font-size: 1px;
Since Firefox uses the font size to determine scroll distance, this page scrolls really slowly in FF.I think this is a very important point. Since everything is the same in Lisp, it's nearly impossible to have an idea of what the program is doing "at a glance". In (sane) syntax heavy languages, you can glean a significant amount of information in a short period of time just by scanning the syntax without reading the code.
This is less of an issue when writing a program, and more of an issue when maintaining one.
parseInt('10', {test: 'test'})
10
parseInt('10', 'test')
10
parseInt('10', '2')
2