We've had a number of different widget codes over the years and as such we like to make sure our long time users update their codes to ensure they are getting the best performance possible from the widgets on their site.

About 3 years ago we converted the Javascript code from the traditional synchronous (sync) style to the newer asynchronous (async) style. The async version has the advantage of never blocking loading of page elements on your site, which would have been possible with the sync version.

Although the async code has been available for many years we are still seeing lots of sites using the sync version, so we'd like to provide this message to assist users in determining what sort of code they are running.

If the whos.amung.us widget code installed on your site looks something like the following code you are using the old sync version and we recommend you convert to the async version. Note: the code below is an example only, it shows a dummy site identifier (123456789012) and is for the small widget, the other types have slightly different formats.

<script type="text/javascript" src="http://widgets.amung.us/small.js"></script>

<script type="text/javascript">WAU_small('123456789012')</script>

If your code looks something like the following (again, this is an example, it will vary from widget style to widget style) then you are using our async code and all is good :)

<script id="_wau3b8">var _wau = _wau || []; _wau.push(["small", "123456789012", "3b8"]);

(function() {var s=document.createElement("script"); s.async=true;

s.src="http://widgets.amung.us/small.js";

document.getElementsByTagName("head")[0].appendChild(s);

})();</script>

We'd be happy to help you convert the code on your site to the async version if you are still using the sync version, feel free to contact us.

If you need a new widget code, just grab one from the showcase to ensure you have the latest code!

We've added a pie chart to your stats dashboards showing the breakdown of user devices to your site. We've broken the device down to the critical ones (phone, tablet, and desktop) so you can get a sense as to what devices your users are accessing your site with.

We've also provided the data not just for the current moment but also for the past 24 hours so you can see how device usage changes on your site over the day.

There have been reports of some users reporting that a whos.amung.us widget is being added posts they make on their blogs or comments on forums, etc.

This is caused by a browser extension that users have previously installed that adds widget code to comments and posts. The extension often masquerading as Adobe Flash Player (which is not a browser extension/add-on, it is a plug-in) or some other video player type add-on/extension. Users should remove the extension if it is causing them problems, and please contact us with any details so we can get things sorted out.

We do not support adding our widget code to anything other than webpages, adding it to emails, browser extensions, or other software violates our terms of service and is not supported.

Don't hesitate to contact us with any questions you may have.

It's with great sadness that we learned out friends at Wibiya have decided to shutdown their toolbar product. We've worked closely with them since near day 1 and we're honored to work with them by providing our services through their toolbar - even near the end where we were the only third party service provider on the toolbar!

We wish everyone at Wibiya all the best in their future endeavors.

For our users who are currently using whos.amung.us through the Wibiya toolbar, don't worry you can still use our services! Simply grab a widget code from our showcase and replace the site id in the widget code with the site ID your Wibiya toolbar uses (contact us if you need help). By replacing the site id you'll retain all your existing stats.

If you are a whos.amung.us PRO user, you can simply generate a widget code in the "Widgets" section of the PRO Control Panel, and install it on your site.

Don't worry it'll be back very shortly! We're experiencing a problem with a small subset of users accounts and have transitioned those to a backup system while we get things straightened out ASAP!