71–80 of 181 posts
Obvious question - how was the list of URLs compiled? Some are really specific like YouTube channels. On the other hand there are only 15 categories and there are probably a lot of people that would not get a single match or only something very generic like Wikipedia.
fivethirtyeight.com appears about a dozen times for me?
This is mind-blowing, mine was pretty accurate! I know I can view the source code, but is this/similar code available from GitHub or somewhere for us to use in our own weekend projects? (:
Question: I know that the `:visited` exploit is handled by the browsers so that you can't figure out by javascript what is going on... but what if you used just CSS to figure it out? For instance, what if you generated the CSS which had a unique image it requested via the `background-image` property, stored the data on the server, then just requested the data from the server after the fact? Do the browsers prohibit t…
Yes, they prohibit anything that might be used for this purpose.[0] So the CSS allowed for :visited selectors is limited to a small subset. [0]: https://hacks.mozilla.org/2010/03/privacy-related-changes-co...
Your interests are: (some subset of) Programming Science Technology Games
With literally no scripting, and everyone would find it "reasonably accurate" :D
Wao, reading my browser history while I am playing a stupid game. Elegant. :)
I thought the a:visited exploit was addressed.
I spent an unfortunate chunk of time trying to auto-click all the red square via jquery in chrome console. After a lot of reading and experimenting, I can verify that the exploit is thoroughly addressed (so far), and I cannot achieve my goal because of it :(. The most promising workaround would be to find a JS screenshot tool that doesn't rely on the DOM, and then run some client-side image analysis to get the index…
Earlier quoted context omitted.
For a less "covert" example than I am sure the OP was thinking, you could have "click the red button to continue" sort of like this page does. :)
Wouldn't that also require a hundred same sized differently colored buttons, just like this site?
That's what I think he meant.
Question: I know that the `:visited` exploit is handled by the browsers so that you can't figure out by javascript what is going on... but what if you used just CSS to figure it out? For instance, what if you generated the CSS which had a unique image it requested via the `background-image` property, stored the data on the server, then just requested the data from the server after the fact? Do the browsers prohibit t…