Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderI disagree that just because its possible for a malicious or comprimised server to send evil javascript, javascript crypto should not be done. You have to analyze the threat model. Take the note taking webapp they use as an example. Without javascript crypto, anyone who breaks into the server can read everyones notes. Likewise, the FBI can get a warrant and have the owner of the web application turn over everyones notes. If they do use javascript crypto, instead of…
This piece has surfaced before. Then and now I see people coming out of the woodwork with seemingly smart ideas about how it still should be possible to safely use crypto in the browser one way or another. One of the things my company does is security testing of web applications. Regularly we encounter 'creative' use of cryptographic techniques (both in the browser and server-side) and each time it makes the hacker in us smile, because we know it is…
Isn't kind of the height of stupidity to attempt to secure transactions on any client-side app? - a javascript developer
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 223
- Total comments
- 244
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2013-01-27 | Javascript Cryptography Considered HarmfulFirst breakout | LVB | 95 | 103 |
| 2014-06-17 | JavaScript Cryptography Considered HarmfulBest thread · Latest 20+ point return | mazsa | 127 | 140 |
| 2017-05-22 | JavaScript Cryptography Considered Harmful (2011 – still relevant) | ColinWright | 1 | 1 |