Live data from Hacker News

Viewing profile — jaeming

jaeming

HN member
Joined
Sun, Sep 28, 2014, 11:54 AM UTC
HN karma
365
Public activity
60 items

About jaeming

No profile information was provided.

Recent public activity

  1. comment
    Comment #42867678

    I was one of those that really felt like Runes was going to ruin svelte. But after working with it on a small team for a month now, I can see the benefits. We previously had a lot …

  2. comment
    Comment #41140897

    The post presents this like it's a novel and noble idea. Yet, nowhere does it mention the term severance(or redundancy pay). I guess I should applaud them for voluntarily following…

  3. comment
    Comment #41140836

    One of the biggest issues we have with Rails these days is finding Rails devs (at least where I work). Our next project's backend may very well have to be Node or Python specifical…

  4. comment
    Comment #37593956

    Yeah, you know that thing Vue did with the composition API that a bunch of their users didn't like and then subsequently turned to Svelte over? Well, it turns out they were right a…

  5. comment
    Comment #37080927

    Thanks for the re-assurance. We've been migrating a huge app to svelte over the last 6 months and it's nice to hear it won't be become legacy on arrival ;) Looking forward to the e…

  6. comment
    Comment #32416769

    As someone who worked for over a decade in post-production, I can tell you this was most likely edited on FCP 7 because it was considered the better tool and not because of cost co…

  7. comment
    Comment #31956843

    What I am not overlooking is that they as a company and in this comment have an implicit bias against Dev's rolling their own auth since their business model is based on them not d…

  8. comment
    Comment #31956806

    Mitigating an attack is really, really, really hard. How hard is it? What are the challenges? Could you be more specific? Cause I keep seeing the blog and article headlines telling…

  9. comment
    Comment #31956734

    captcha integration is super easy and doesn't require a full auth integration service. Detecting a brute-force maybe less so maybe, though I get a lot of DDOS pretection for free w…

  10. comment
    Comment #31956708

    There's a lot of food for thought there and I can actually get on board with a lot of what you said. I enjoyed your perspective at the very least. I too have been a part of some to…

  11. comment
    Comment #31936596

    What I mean by tightly coupled, is if you can have your Frontend and Backend on the same domain, then yes by all means an httpOnly cookie is ideal. Now days there are a lot of SPA'…

  12. comment
    Comment #31929317

    Auth is actually a combination of two things: authentication and authorization. Whatever you do, please do not build either by yourself. It's blanket statements like this that real…

  13. comment
    Comment #31929243

    Existing crypto libs like bcrypt, which I mentioned? Or are you talking about something more? The credential stuffing mention you make makes me think you must mean something more. …

  14. comment
    Comment #31929217

    I mean, yeah, sure. Or for a number of other use-cases. I'd argue the best way is for the client to keep the token in memory over local storage. Of course if you have a tightly cou…

  15. comment
    Comment #31929205

    I mean, it's stored in a DB somewhere, even if it's not your own. I would argue your own DB probably has less of an attack vector than major providers.

  16. comment
    Comment #31929190

    I don't quite follow the moral here. Was the Dev who rolled their own auth back when MD5 was the norm supposed to time travel forward to a time when cloud services like Auth and Co…

  17. comment
    Comment #31929156

    Oh yeah, for sure, there are a really good libs. Someone mentioned passport. I've personally used Devise/warden in Rails. Though we had to monkey patch/extend it so much that 6 yea…

  18. comment
    Comment #31929116

    Too true and worthy of a rant of all it's own...

  19. comment
    Comment #31929093

    I've never head that adage. I did hear one from Miles Davis that says, "If you have to ask, you'll never know." I ask a lot of questions though so I never paid much attention to ol…

  20. comment
    Comment #31929051

    Yeah, that's why I prefaced with "the basics of auth are actually pretty easy". Rather than trying to opt-in to those other auth flows before you need them, I'd suggest starting wi…

  21. comment
    Comment #31929040

    Two factor is actually pretty easily solved too though?

  22. comment
    Comment #31926239

    There's nothing wrong with JWT as a token spec. I prefer stateful sessions as well but but a stateless token also serves specific use-cases. It has also become a standard practice …

  23. comment
    Comment #31926195

    I agree, stateful sessions can handle a number of problems and use-cases more gracefully. I work with a lot of api's the service multiple clients though and I do see a use-case for…

  24. comment
    Comment #31926153

    Yes, that's why I said "the basics are really easy"? This was not meant to imply 10 lines of code handle the complete user experience workflow around auth. In saying that I have im…

  25. comment
    Comment #31926130

    I didn't advocate for storing your session in local storage. I posed it as a question.