161–170 of 181 posts
Hm. Do you really need interaction at all? Can't you just :visited { margin/pos/whatever }, then probe the dom on that or related elems to extract the juice? Or have browser vendors thought of this?
If nothing else, I did get a good list of Programming and Engineering websites :D - http://pastebin.com/zrQ7EBnP
Here's the same exploit disguised as a game, to make it less obvious that it's tricking the user into interacting with it: http://lcamtuf.coredump.cx/yahh/ Documentation of the game proof-of-concept: http://lcamtuf.blogspot.com/2013/05/some-harmless-old-fashio...
If nothing else, I did get a good list of Programming and Engineering websites :D - http://pastebin.com/zrQ7EBnP
This is OT, trivial and a bit silly: How did you intend the json file? I tried with sublime but couldn't find anything to solve it. Didn't start an IDE for this.
Otherwise, there's always sites like http://pro.jsonlint.com/
I could probably post a similar gizmo on HN with a results static page that says Your interests are: (some subset of) Programming Science Technology Games With literally no scripting, and everyone would find it "reasonably accurate" :D
Earlier quoted context omitted.
You could access the webcam and zoom/enhance the reflection in the eyes to get the screenshot.
Think I just found a way using canvas with a semi transparent element inside of it, then overlaying that on each square, grabbing the computed/resulting color of the canvas to decipher which block is what. S O O N
http://jsfiddle.net/path411/sRkWq/
It appears as though Chrome (37-dev) will not receive any data from behind the canvas, while IE11 and FF(29) will allow me to see pixels behind the canvas, but only see the unvisited color.
I don't believe there is another method to receive the color of a pixel from a canvas except through getImageData(), but I could be wrong.
If you open the console and run this script, it'll click every single square, giving a list of the most common types of sites in the array being used: for(i=0;i
I had to change it to start at i=1 to avoid clicking on the link to github and leaving the page
Hm. Do you really need interaction at all? Can't you just :visited { margin/pos/whatever }, then probe the dom on that or related elems to extract the juice? Or have browser vendors thought of this?