Live data from Hacker News

Viewing profile — kcen

kcen

HN member
Joined
Fri, Jun 22, 2012, 9:36 PM UTC
HN karma
53
Public activity
20 items

About kcen

No profile information was provided.

Recent public activity

  1. comment
    Comment #27902903

    Sounds too complicated to do with a reasonable type system and autocomplete, should probably use ML.

  2. comment
    Comment #26432417

    Can we then write off the motorcycle sim racing rig as office equipment?

  3. comment
    Comment #23756166

    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. story
  5. story
  6. story
  7. story
  8. comment
    Comment #6730033

    Looks like you can sign up just fine with only an email address.

  9. comment
    Comment #6722768

    This looks pretty close to a clone of the Sequel gem. http://sequel.jeremyevans.net/ https://github.com/jeremyevans/sequel

  10. comment
    Comment #6693705

    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 …

  11. comment
    Comment #6657870

    I assume when Jordan gave them his address they knew he would actually want the stuff...

  12. comment
    Comment #6614548

    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…

  13. comment
    Comment #6441222

    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 provi…

  14. comment
    Comment #5910090

    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 yo…

  15. comment
    Comment #5909963

    It's always the new guy, f'n new guy.

  16. comment
    Comment #5909838

    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, nam…

  17. comment
    Comment #5805723

    For the Rails folks out there, I have had pretty good luck with Brakeman Scanner in the past. http://brakemanscanner.org/

  18. comment
    Comment #5688651

    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.

  19. story
  20. story