It's actually a client-side issue that's been messing with us on and off for some time now. We'll get it sorted out for the 2.0 release.