Show HN: Honeybadger Chrome Extension
gethoneybadger.com
gethoneybadger.com
This site was created using a bootstrap theme that had her picture in there FWIW.
Except for this snippet of code in popup.js of course.
var _gaq = _gaq || []; _gaq.push(['_setAccount', 'UA-40692955-5']); _gaq.push(['_trackPageview']);
Edit: I tested this with a console.log, and it output immediately on page load, without clicking anything.
I just checked my personal site and it came up with technologies I've never heard of. It also said I use 'bitpay' for payments
http://gethoneybadger.com:8080/whois/ox.ac.uk
http://gethoneybadger.com:8080/whois/cam.ac.uk
http://gethoneybadger.com:8080/whois/dur.ac.uk
(This list might help to uncover other problems like this: https://publicsuffix.org/)
I wonder how many testimonials on the web are actually real?
88.231%, which is a bit higher than the number of made up statistics, coming in at 71.9231%.
For the extension itself: I like that it doesn't call out for information unless called upon, but if I ask for information about a site, I see no reason for you to have to collect the full URL and POST it to /track. That could lead to unexpected data leakage (as some URLs could be sensitive). You should probably get those API calls over to using HTTPS as well.
Also with every lookup, my console gets the log message "asdf", which is kind of weird. One thing I noticed is that the extension is pretty slow to get information. It appears it calls out for each item individually, and this leads to seven unique calls to your API that could be condensed into one request / response. If an API call fails with a 500 error, the entire stacktrace is dumped to the user. You'll want to disable debugging mode in your Express app to ensure that doesn't happen.
Since these APIs are public, you might want to consider rate limiting by IP, or you might find that your extension isn't the only consumer of them. A free and open WHOIS or Geolocation API that responds with JSON could be abused by other app developers, and having that already around moves the cost from them to you.
Even if the similarity was completely inadvertent, it's just going to lead to confusion and legal hassle, and could end up hurting your reputation more than the functionality of the extension will help it.
It's also catchier - might make a better product name.
Added: using the same orange helped the deception.
www.builtwith.com provides much more information but they do not have a chrome plugin that I'm aware of. Definitely should check it out if your interested in this plugin.
Edit: For what it's worth, if the plugin really does what it says it does on the Chrome Webstore page, it sounds really, really useful. Will try later.
/s