Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

As a well-known person on HN, that amount of snark is unbecoming of you. FWIW, you can bork your own system just as much, if not even more so, with HSTS headers. And also with DNS in general; how many people have mucked up a DNS setting and then have no recourse but to wait it out? The issue was not DNSSEC, but Slack who panicked and pulled the plug on themselves.


It's not snark if you're mocking the person you're talking to. That's just disrespect. Maybe he's had bad experiences in the past with DNSSEC that are causing him to forget himself. I feel like he's been talking down to me too.


Read it again. I'm not "mocking the person I'm talking to". I don't even know the person I'm talking to. I'm mocking the statement they made, that DNSSEC is fine, and when it blows your whole site off the Internet because you dared turn it off after it immediately caused problems the moment it was turned on, well, you were just holding it wrong. It really is funny! Read their comment again, too!

I suppose I could be less snarky, but my snark here is substantive, and I'm comfortable with what it says about my seriousness. You're going to have to do better than trying to work the refs here.


DNSSEC is continuing to have a bad experience with tptacek, really. The Rorschach of DNSSEC, if you will.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: