3 ms·
The JS code sent to kentonv's browser might be safe, but you can't really meaningfully comment on hobs' situation, since you don't have a copy of the JS code th
by desdiv 11y ago
The JS code sent to kentonv's browser might be safe, but you can't really meaningfully comment on hobs' situation, since you don't have a copy of the JS code that was sent to hobs' browser.
- kentonv 11y agoActually I can. The author of this code is a friend of mine who works with the EFF, and the idea that she's secretly sending malicious scripts to some people but not others from her MIT web hosting space under her own name is simply not plausible.
- e12e 11y agoUnless, she's already compromised your browser and the two previous comments are in fact placed by her! In all seriousness, I appreciate the added context your (particularly this last clarifying comment) add to the discussion.
- robzyb 11y ago> The JS code sent to kentonv's browser might be safe, but you can't really meaningfully comment on hobs' situation [...] But if that's the case then you shouldn't click on anything on HN. I would argue that it is A-OK to post this link directly on hackernews. It just says "look at what your browser can do! imagine if blackhats took advantage of this."
- bcrypt 11y agoIn any case, I didn't minify or remove comments, so you can just view-source:http://zyan.scripts.mit.edu/sniffly/index.js http://zyan.scripts.mit.edu/sniffly/index.js