Live data from Hacker News

Viewing profile — jamessocol

jamessocol

HN member
Joined
Sat, Jun 09, 2012, 1:19 PM UTC
HN karma
177
Public activity
37 items

About jamessocol

No profile information was provided.

Recent public activity

  1. story
  2. comment
    Comment #7393202

    I'd love to hear—maybe I missed another blog post—why they went with the single release manager, where only one person can merge and deploy. What happens if Doug is sick or on vaca…

  3. comment
    Comment #7105931

    Check out OpenHatch http://openhatch.org/ . Connecting people with time to projects with need is a big part of what they do.

  4. comment
    Comment #5248795

    Consider it? Definitely. But semver doesn't make a distinction, either, so it's a hard problem. If you don't mind, we'd love to get your thoughts more via email--don't want to hija…

  5. comment
    Comment #5248584

    (Disclaimer: I'm the other guy behind BundleScout.) The Django project does a fantastic job with announcements. (So does Rails.) And if every open source project had the infrastruc…

  6. comment
    Comment #5201822

    Thanks for the feedback! We'll definitely look at the right way to surface more info before signing up. (For the record, it's $5/month.)

  7. comment
  8. story
  9. story
  10. comment
    Comment #4292373

    I agree with all of your advice about hardening most servers, but a couple of things... > In the case of PHP, there is no security concern by it just sitting on your hard drive. It…

  11. comment
    Comment #4292345

    >> Are directories only writeable by the web server user? NB: The next point is "Do all of them even need to be? Are you sure?" > A blisteringly common one not mentioned is databas…

  12. story
  13. story
  14. story
  15. comment
    Comment #4267665

    Honestly, "easy to overlook" is why I wrote a checklist for basics. CYA, then get to the advanced stuff.

  16. comment
    Comment #4267661

    We keep making more junior devs. It's important to drown out the w3schools and bad practices with good practices, so when they look up how to do it, they learn the right way.

  17. comment
    Comment #4267639

    Like I said elsewhere, that's a major cost/benefit calculation in terms of both real cost and user experience/conversion rate cost. If it makes sense for your app, do it, but it's …

  18. comment
    Comment #4266635

    For click-jacking, the easiest thing to do is to set the X-Frame-Options header, but I'll get to that. And it doesn't help IE And we'll get to session hijacking and why your sessio…

  19. comment
    Comment #4266493

    I updated the post to point this out.

  20. comment
    Comment #4266466

    Hopefully you're taking steps to prevent both. But yes, closing the CSRF window and leaving the XSS door open would largely defeat the purpose of CSRF protections.

  21. comment
    Comment #4266396

    Ugh, I really need to create a lighter-weight theme. Sorry about that.

  22. comment
    Comment #4266383

    > In order to issue a POST request to siteA from the evil page, the attacker only has to submit a crafted POST form using an iframe. Yes, but requiring POST for anything that chang…

  23. comment
    Comment #4263671

    Maybe we come from different backgrounds. Using open source code that's been subject to lots of eyes and lots of use, e.g. a framework like Django, reduces the surface area, to me,…

  24. comment
    Comment #4262451

    > Relying on tools or, in fact, any code you've not written yourself makes your system vulnerable. Writing everything yourself, as opposed to widely, community tested open-source a…

  25. comment
    Comment #4262398

    It's the weird combination of gettext, HTML, and user-supplied data that causes problems. But yeah, kind of surprising there isn't already something. That's why we moved the |fe fi…