Another company steps up.

Nike has been diligent in trying to provide a better experience for customers shopping on NDC and they might have gotten some unexpected help. Nike has even tried implementing the CAPTCHA system to slow down bots which has been somewhat successful, but since have employed other methods that haven't worked out so well.

Last November, Google issued a warning about an upcoming policy which automatically disables unauthorized Google Chrome extensions and gives developers up until May 2014 to make sure they meet the Web Store guidelines. If their Chrome extensions didn't meet the Web Store guidelines then they are not allowed to reauthorize that app for further use.

Extensions that were previously installed, but not hosted on the Chrome Web Store will be hard-disabled (i.e the user cannot enable these extensions again) - TNW

How does this Google Chrome policy change effect bots you might ask? Well if the bot someone is trying to sell you isn't present on Google Chrome Web Store then chances are it has been disabled and won't work on your computer. Now the least of Google's worries are sneakerheads trying to gain an advantage while shopping for heat, but they are concerned about privacy and malicious software included in third party extensions running in their browsers. As of the release of Chrome 35, if you were previously using a bot (in other words a third party extension) on a Windows computer, it has been blocked unless the developer got it approved on the Google Chrome Web Store.

Windows users are the first guys screwed out of their bots. Bot users on operating systems other than Windows haven't seen this policy change yet, but expect Google to roll one out across all platforms soon.

This doesn't mean an immediate end to bots, but it is a major set back for cheaters. Google is very aggressive toward policy changes if developers with ill intent start to effect the experience of their users, so if you're tired of complaining to Nike, try giving Google some feedback.

Read full Google Chrome policy update here.

Shout out to @franchise_davis for bringing up the conversation.