bascule

65 ms·

511.
by bascule 15y ago
There's so much wrong with this article I don't even know where to begin. I guess I'll start with: "In most implementations, the data sent to actors must be immutable." This is true of Erlang. It's not true of many other actor systems, incl
512.
by bascule 15y ago
Because unless you have an unusually high (>1000) concurrency level for your HTTP connections, threads are a more than adequate solution to the problem.
513.
by bascule 15y ago
Obviously you're going to rebuild compromised servers and change all the keys... as soon as you find out you've been hacked. What about before then? You're advocating a scheme whereby if any verifier is compromised, the attacker can forge t
514.
by bascule 15y ago
Can you please explain why using DSA to sign SSO tokens is a bad idea?
515.
by bascule 15y ago
Are you familiar with Pow? http://pow.cx/ It also happens to be written in JavaScript
516.
by bascule 15y ago
> I don't want to have one process per request, so the obvious thing was to use something asynchronous There's these amazing things called threads you can use too
517.
by bascule 15y ago
I'm confused, what does this post have to do with Ruby, other than a brief mention about how Ruby's syntax is different from other languages?
518.
by bascule 15y ago
BrowserQuest, which is written in Node, put their inventory tracking system client side. Brilliant! http://www.raymondcamden.com/index.cfm/2012/3/28/How-I-cheat...
519.
by bascule 15y ago
Strongly agree, Memepool was a great well-curated archive of stuff I typically didn't see anywhere else. I <3ed it.
520.
by bascule 15y ago
The only dangerous part of git reset is git reset --hard, which will blow away uncommitted changes. It has a special flag for a reason... it's dangerous. Beyond that, git reset won't get you anywhere that you can't get back to after consult
521.
by bascule 15y ago
Sure, and if you want to have a better user experience, manually add those certificates to the ones you trust, then you won't get the warnings.
522.
by bascule 15y ago
Here's an idea, instead of building anything that moves, how about building a cheap, disposable server you can install covertly anywhere you want that automatically dials home after installed and can use WiFi or Ethernet? http://pwnieexpre
523.
by bascule 15y ago
I thought I explained that in my blog post. scrypt is superior to bcrypt in every regard. At the very least, I'd rather the meme be: Use bcrypt, scrypt, or PBKDF2.
524.
by bascule 15y ago
I fully admit the title is linkbait. My goal was to get people interested in the alternatives to bcrypt.
525.
by bascule 15y ago
You're defending cargo cult cryptography? If you try to use crypto without understanding it, you're at great risk of using it wrong.
526.
by bascule 15y ago
I can't speak for other platforms, but at least as far as Ruby goes: $ gem install scrypt Building native extensions. This could take a while... Successfully installed scrypt-1.0.3 1 gem installed
527.
by bascule 15y ago
These are all valid criticisms. Apologies for using "cipher" where I meant "algorithm"
528.
Don't use bcrypt(unlimitednovelty.com)
177 points by bascule 15y ago|188 comments
529.
by bascule 15y ago
I had exactly the same reaction. Is this article going to be about Konrad Zuse? Oh look, IT IS!
530.
by bascule 15y ago
The best part of this is the area of a circle, which is the integral with respect to r of r tau, or tau r^2/2. Sure, pi*r^2 is nice and easy to remember, but also remember even the mnemonic is wrong... pies are round!
531.
My problem with Hacker News(i.imgur.com)
12 points by bascule 15y ago|3 comments
532.
by bascule 15y ago
"Depressing" is about the last feeling I wanted to leave someone with after reading this article. I really wanted it to be upbeat.
533.
Why critics of Rails have it all wrong (and Ruby's bright multicore future)(unlimitednovelty.com)
51 points by bascule 15y ago|3 comments
534.
by bascule 15y ago
It's a write that shouldn't be authorized but was. It's an access control vulnerability, and they happen all the time.
535.
by bascule 15y ago
The scaffold Rails generates isn't insecure by default, it just doesn't automatically generate example cases that require input validation. Perhaps it should be laden with comments about how to validate input when your code does eventually
536.
by bascule 15y ago
Ensuring input is properly validated is always the developer's concern. A framework can make that easier for you, but especially in cases like this, which are basic user authentication concerns, it is ABSOLUTELY the developer's responsibili
537.
by bascule 15y ago
You do know what HTTP keepalive is, right?
538.
by bascule 15y ago
There's no need to benchmark. Everything written in Node.js is insanely fast by default, because nonblocking is the secret to the roflscale sauce.
539.
by bascule 15y ago
Hell yes Kraftwerk!
540.
by bascule 15y ago
It's a hard metaphor to pull off. Cut my some slack :) The real point I'm trying to make is just if you want to test somebody's ability to write code, give them a computer, don't make them code on a whiteboard. If you're actually using a wh

More ›