81–90 of 181 posts
I get the same three red boxes in Chrome every time, and none in Firefox or Safari. I get three categories at the end, with no links or anything. What am I doing wrong?
I get the same three red boxes in Chrome every time, and none in Firefox or Safari. I get three categories at the end, with no links or anything. What am I doing wrong?
This works by showing you a grid, each box represents a website, to which the creator has ascribed a category(tech/gaming/etc...)
If you've visited one of those sites the box will appear red, and by clicking on the box you let the site know that it is something you've visited in the past and therefore likely one of your interests.
Was on incognito and wondering why I didn't see any red squares...
That is, I am guessing, because there aren't any re-marketing cookies,history and other markers when you open the page in incognito
This web-app's functionality is based entirely on browser history and has nothing to do with 're-marketing cookies' or other 'markers'.
Not to mention that the parent commenter clearly understood this fact.
Heh. I clicked a few before I realized what was going on (looking at the status bar shows the link, which somewhat gives it away). You could prevent this by adding mouseover/out and onclick logic that removed the :href on hover and just colored itself red.
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? (:
I hope to clean up the code and post it to GitHub tomorrow.
This is quite clever. By the way now I've got a nice list of blogs/websites that I should probably read for various topics.
It was eerily accurate on me. 1. science 2. technology 3. programming
1. technology
2. movies
3. books
4. programming
5. science
6. politics
7. gaming
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…
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