4 ms·

I fully agree it is a research paper and the subject matter is absolutely great! My complaint is the research paper hints at what may be affected in the abstrac

I fully agree it is a research paper and the subject matter is absolutely great! My complaint is the research paper hints at what may be affected in the abstract, that got picked up in the title, and then it got a challenging to find actionable details quickly for either an end user or someone only mildly interested in the topic. It also liked to a github page which is a great place include the short non-research content. I think the github page was WIP at the time the article appeared on hn. I know my attitude was critical, but I also tried to include that info in the message (even though I found the responsible disclosure subsection after posting my original comment). I also feel that info should be present on HN in one of the top comments for these kinds of articles (regardless of whether it's mine or someone else's).

est31 4y ago
> It also liked to a github page which is a great place include the short non-research content. I think the github page was WIP at the time the article appeared on hn. I see. When I made the reply it already linked to the pdf. So you can't really be blamed neither can I. Such confusion is normal when a link changes. > I know my attitude was critical, but I also tried to include that info in the message To be fair, hn is renown for that attitude. Some of the most famous hn comments are precisely of that kind :) https://news.ycombinator.com/item?id=9224 https://news.ycombinator.com/item?id=9224 The paper was written to suit an academic audience first, which includes people reading it 20 years later. Actionable advice for users is then in accompanying notices. Also, usually when papers get published, it's months after they have been submitted so usually security bugs are already fixed and if you are on somewhat up-to-date patch levels, you are safe. I say usually because some vendors might not be as quick to patch or it might not be as easy to fix bugs (say bugs in hardware or such).

est31 4y ago

> It also liked to a github page which is a great place include the short non-research content. I think the github page was WIP at the time the article appeared on hn. I see. When I made the reply it already linked to the pdf. So you can't really be blamed neither can I. Such confusion is normal when a link changes. > I know my attitude was critical, but I also tried to include that info in the message To be fair, hn is renown for that attitude. Some of the most famous hn comments are precisely of that kind :) https://news.ycombinator.com/item?id=9224 https://news.ycombinator.com/item?id=9224 The paper was written to suit an academic audience first, which includes people reading it 20 years later. Actionable advice for users is then in accompanying notices. Also, usually when papers get published, it's months after they have been submitted so usually security bugs are already fixed and if you are on somewhat up-to-date patch levels, you are safe. I say usually because some vendors might not be as quick to patch or it might not be as easy to fix bugs (say bugs in hardware or such).