Just a quick note to wish you all Merry Christmas and a Happy New Year. The office will be closed from Friday December 21, 2014 to Sunday January 7, 2015. We’ll be back and into things on January 8th. If you need support during this time then please use our shiny new support system that went live today either via the email@example.com email address or via the support widget from the website.
A few hours ago we were alerted to a serious security breach in Handset Detection which allowed authenticated users (anyone logged in) to view and potentially edit any site in the system. No user, billing, payment or contact information was accessible. Only site information. The bug was introduced in a rework of our access control system for a few up coming features, released yesterday afternoon. We’ve combed the logs and identified that 5 sites were ‘admin viewed’ and only one site was ‘admin edited’, by the person reporting the problem (on their own site).
Heads up, mobile developers! In a recent blog post, Google announced that they were going to start penalizing sites that are misconfigured for smartphone users, in mobile search. Problems, Problems Fortunately, they didn’t leave us hanging, and detailed the two most common smartphone configuration errors, the first of which was the always-frustrating faulty redirect. This happens when someone clicks a link to your site from search but doesn’t end up on the equivalent page on your site.
Shortly we’ll be making a few changes to our device database to improve device classification and make our naming more straight forward. First and foremost all generic device profiles will now have the vendor set to Generic. This will mainly impact Android devices which were previously referred to as vendor ‘Android’, model ‘Generic’, now they’ll be vendor : ‘Generic’, model ‘Android x.x Mobile’. Which is a little more specific than before.
We’ve grown by leaps and bounds since our humble beginnings in 2008, but our next step is to make sure we’re growing with our customers. As you see more and more mobile handsets detecting your websites and online stores, you most likely see new challenges and have new questions. That’s why we need to hear from YOU! Take our survey to let us know what you’re looking for an for a chance to get a sneak peek at new Handset Detection features before they go live.
Just a quick note to let you know that we’ve had a glitch in our main stats database for the last 24 hours. Detections were being counted while stats were not being logged (they sit in different databases). The cause has been found and the problem fixed. However, it will take a few days to reconstruct stats for the last 24 hours from detection history and get them into the database.
Earlier this week Handset Detection experienced intermittent outages, delayed service and high network latency (for the non technical people out there thats basically all bad). The actual problem was a 3 fold combination of a traffic surge (which we would usually have ample capacity to handle) combined with a caching bug and the accidental removal of a default device profile by one of our handset maintainers. The system, when looking for this default profile, would rebuild the device cache and save it.
We are experiencing a problem with rollover of detection quotas at the end of account period. All monthly limits have been reset to zero while we trouble shoot the issue to keep the detections a flowin’. Cheers Richard Update : The period rollover issue has been fixed - Keep the reset counters as a few free detections on us. 🙂