<quote user="0utfl0ws"> It is borderline bizarre that you chose to log this to our console. </quote> As donsorg explained, logging to the console was for debugging, and it was mistakenly left there during development. If I understood correctly, a new version which solves the problem has already been...

<quote user="Tuan Jinn Nguyen"> WOT for whatever reason shouldn't have done it without announcement. </quote> Shouldn't have done what? Pretty much every web service is running experiments to test new features with a small, random sample of users. It's an unobtrusive and effective way to see which f...

<quote user="IssViews"> So, suffice it to say, this experimental add-on appears to be extending the website 'similar sites' feature which should be optional and not pushed upon users in a toolbar. </quote> The add-on is not experimental (or a toolbar), and this has nothing to do with "similar sites"...

Good morning guys, This script in the Chrome add-on is part of an experiment we are running on a small subset of users where the add-on recommends you trustworthy (based on user ratings, as usual) alternatives if the website you are visiting matches certain criteria. These are not exactly ads, and t...

The add-on does resolve short URLs for ratings next to links, for example. Where exactly do you see this problem?

We will take a look. It looks like the add-on is blocking our network requests completely on their proxy site.

Can you test if our servers are accessible from Chrome?

This has nothing to do with the font, these are fullwidth Unicode characters. Copying the text to your browser's address bar only works, because the browser folds the fullwidth characters back to normal ASCII, and our search field does not. However, should you open the scorecard from the add-on when...

Clear your cookies and try again.

It has been queued for update, takes ~three days.