bluegate010

7 ms·

1. 31.▲
   by bluegate010 11y ago

   Hey HN, I'm one of the authors on this paper. I'd be happy to answer any questions.
2. 32.▲
   by bluegate010 11y ago

   Hey HN, I'm one of the authors on this paper. It's been making the rounds on Reddit [1] and most recently Buzzfeed [2] so I thought I'd post it here. I'm happy to answer any questions. [1] https://www.reddit.c
3. 33.▲
   Evaluating the Usability of a Modern PGP Client [pdf](arxiv.org)

   2 points by bluegate010 11y ago|1 comments
4. 34.▲
   Artillery Practices by the Major Combatants of WWII(etloh.8m.com)

   76 points by bluegate010 11y ago|38 comments
5. 35.▲
   by bluegate010 13y ago

   Yeah, it's self-referencing, but it's called just before being passed into setInterval. Here's a screenshot: http://i.imgur.com/oh84ZLV.png
6. 36.▲
   by bluegate010 13y ago

   I've got the same problem: Version 30.0.1599.101 Chrome on Mac OS X Mavericks. I believe the problem is your time() method on line 189 of script.js; there's no element with id "time".
7. 37.▲
   by bluegate010 14y ago

   That's what Mega seems to be doing in their initAll() function, although since it's being audited with Javascript, it's still insecure.
8. 38.▲
   by bluegate010 14y ago

   Agreed. Very sloppy code.
9. 39.▲
   by bluegate010 14y ago

   The Javascript for Mega looks very messy; all resources loaded via XHR, loading jQuery but using `document.getElementById` all over the place, using client-side Javascript to validate the integrity of all these XHR-loaded resources... They