51–56 of 56 posts
Out of curiousity, how do you prevent the case of some random malicious user impersonating your chrome extension and just issueing a bunch of "dwells" to your server. I.e. can I just curl what this javascript file (https://github.com/blippex/blippex_plugin_chrome/blob/master...) is requesting to boost my own pages ranking?
Thanks for building this. We need more stuff like this. Out of curiousity, how do you prevent the case of some random malicious user impersonating your chrome extension and just issueing a bunch of "dwells" to your server. I.e. can I just curl what this javascript file ( https://github.com/blippex/blippex_plugin_chrome/blob/master... ) is requesting to boost my own pages ranking?
-Gerald, CTO archify/Blippex
I had a similar idea in college which was to take the actual traffic for pages into account for search ranking (this was before Google bought whatever Analytics had been called before, I can't remember.) I had thought of it as a server side app which would benefit the hosts while feeding the search engine traffic data. After talking with friends we explored the idea of a user side traffic tracking app as a way to fee…
Doesn't work at all without cookies. Meaning, it doesn't work, and doesn't tell you why. If you're targeting people who are looking for an alternative to the major search engines, there's a better-than-average chance that they'll have cookies disabled.
Blippex don't use any cookies, neither the API nor the website. We don't store any data from the people accessing Blippex.
Just disable cookies in your browser, load Blippex, and search. I searched for "shakespeare" in Firefox 22 (where I have cookies turned off), and the result (below the fold, incidentally), was
> Nothing found > We're all like "What the blip, man?" too. ...
Same search in Chrome 28 works fine (and interesting, too).
This is my pet peeve on the web, and so common with HN posts that I don't usually bother to point it out. But this seems like something you'd want to know.
1. PRISM? 2. Often best sites are the ones I spend the least amount of time on—because I got an answer quickly. Would hate to not be able to find those site. Seems link the traditional form of ranking should still be an important part of your solution.
Maybe, we don't kmow yet, need more data :) we also weight the number of visits in the dwell factor, but maybe we have to adapt this in the future.
Thanks for building this. We need more stuff like this. Out of curiousity, how do you prevent the case of some random malicious user impersonating your chrome extension and just issueing a bunch of "dwells" to your server. I.e. can I just curl what this javascript file ( https://github.com/blippex/blippex_plugin_chrome/blob/master... ) is requesting to boost my own pages ranking?
We have some rate limits at our API in place, but of course it not that difficult to change an IP-address. But most important we wrote some algorithms which checks submitted URLs and domains for suspicious or accelerating behaviour. If that happens we simply suspend that domain for some time. We are also planning to publish those suspensions. -Gerald, CTO archify/Blippex