[10:42] http://yro.slashdot.org/story/12/03/17/0142219/websites-can-detect-what-chrome-extensions-youve-installed [14:01] I'm so glad we chose Javascript for our web language. :) [14:03] I was worried when we decided to move from PHP to other languages that we'd make the web more secure. ;) [14:20] psh, what security issue is it you've run into? [14:20] See scrollback from brousch [14:22] this isn't anything JS related, just how chrome does extensions [14:27] i'm learning things about python that i'd never thought about before. [14:27] like from module import name <-- what that ACTUALLY does. [14:27] its interesting [14:27] very C like, very java/c# unlike [14:28] gonna be hard to get a buffer overflow in js :) [15:58] jrwren: heh, import magic! [16:01] rick_h: Yes but the extensions are written in JS, correct? [16:04] snap-l: right, js and html, but he's reading your manifest.json file, which is required for the extension. So chrome should just prevent access to that file to the running website [16:04] True, this is a problem with how Chrome handles extensions [16:04] right, and nothing to do with JS security [16:04] :P [16:05] rick_h: I can see this getting worse before it gets better. :) [16:05] Javascript is extremely powerful and very well integrated into the browser. [18:16] don't use chrome :) [22:29] Good evenning [23:01] party [23:50] http://blandvargar.bandcamp.com/ <- And this is why I don't play much black metal [23:50] although this isn't the worst I've heard.