kcen

4 ms·

1.
by kcen 5y ago
Sounds too complicated to do with a reasonable type system and autocomplete, should probably use ML.
2.
by kcen 6y ago
Can we then write off the motorcycle sim racing rig as office equipment?
3.
by kcen 6y ago
One of the problems with forcing strictly disparate domain/service is that each one introduces its own security context and authZ handling. That's a lot of places for mistakes.
4.
DockerCon, the first Docker conference. June 9-10(blog.docker.io)
4 points by kcen 13y ago|0 comments
5.
How Many Zero-Days Hit You Today?(krebsonsecurity.com)
1 points by kcen 13y ago|0 comments
6.
Rails 4.0.2 & 3.2.16 released - 5 new CVE's(groups.google.com)
2 points by kcen 13y ago|0 comments
7.
by kcen 13y ago
Looks like you can sign up just fine with only an email address.
8.
by kcen 13y ago
This looks pretty close to a clone of the Sequel gem. http://sequel.jeremyevans.net/ https://github.com/jeremyevans/sequel
9.
by kcen 13y ago
I learned about it from creack (lead contributor according to github) @ a startup meetup in SF. Things that impressed me: 1. super passionate 2. he was very receptive and quick at squashing bugs I reported (real or not) 3. docker was super
10.
by kcen 13y ago
I assume when Jordan gave them his address they knew he would actually want the stuff...
11.
by kcen 13y ago
The primary downside to a small TTL is cost. For many DNS providers you are allotted a number of requests per month that DNS will resolve. On particularly popular websites having a ton of DNS requests can cause the cost of DNS services to i
12.
by kcen 13y ago
It takes just as many people to fly a robo-F16 as it does to fly a manned F16. Only difference is that the pilot is on the ground instead of in the air. Also the unmanned F16 provides 0 advantages over a purpose built UAV (plus is bigger, s
13.
by kcen 13y ago
Isn't that the point of OAuth? (versus HTTP basic auth) Your secret key shouldn't be compromised, because you're supposed to keep that secret. Also if you use HTTPS for requests you'd still get a cert error even if DNS w
14.
by kcen 13y ago
It's always the new guy, f'n new guy.
15.
by kcen 13y ago
The DNS was not exactly hijacked, there were issues inside of LinkedIn's top level DNS provider whom were delegating www.linkedin.com authorization to unauthorized nameservers, namely NS[SOMETHING].ztomy.com. The ztomy DNS replaces its
16.
by kcen 13y ago
For the Rails folks out there, I have had pretty good luck with Brakeman Scanner in the past. http://brakemanscanner.org/
17.
by kcen 13y ago
That way you can safely put your public key on all of your application servers so that any node can write data, but only allowed nodes can read.
18.
One question daily SCRUM(jonathanboutelle.com)
2 points by kcen 13y ago|0 comments
19.
Leading Using Numbers(jonathanboutelle.com)
4 points by kcen 14y ago|0 comments