Lots of new bots
Also found another set of false-positives:
- 360spider
- adsbot
- adstxtcrawler
- awariorssbot
- bitlybot
- boardreader
- ccbot
- cincraw
- clickagy intelligence bot
- crawlson
- crsspxlbot
- datagnionbot
- deskyobot
- df bot
- dnsresearchbot
- duckduckgo favicons bot
- eyeotabot
- feedlybot
- foocrawlerbot
- germcrawler
- google adwords instant
- gumgum bot
- hatena
- hetrixtools
- hubpages
- ias_crawler
- internet structure research project bot
- jugendschutzprogramm-crawler
- krzana bot
- lightspeedsystemcrawler
- linespider
- livelapbot
- lufsbot
- moatbot
- netestate ne crawler
- netpeakchekerbot
- netvibes
- nimbostratus bot
- nixstatsbot
- obot
- odklbot
- paperlibot
- pilicanbot
- pleskbot
- politecrawl
- pubmatic crawler bot
- rogerbot
- scooperbot
- screaming frog seo spider
- semantic-visions.com
- semanticbot
- seolizer
- sirdatabot
- surdotlybot
- tapatalk cloudsearch platform
- tpradstxtcrawler
- velenpublicwebcrawler
- yisouspider
- wp.com feedbot
- zoombot
- Cubot mobile phones added to false positive list (Logicom BOT phones are already on the list)
Lots of new bots, including UptimeRobot suggested by @Nirjonadda. See FAQ for complete list of bots now detected.
New functionality: tool to test bot detection - paste in a user agent string and the tool will tell you if it detects a bot
New bots:
- TelegramBot (thanks @alsogamer )
- InternetNZ Webscan
- Microsoft WinHttp
- Microsoft Office (Excel / Word / etc)
- AspiegelBot (thanks @VersoBit )
Added an option to disable the display of robot statistics in sidebar widgets (which were added in v2.3.0 of this addon)
v2.1.0 updates (unreleased)
v2.2.0 updates
- new bots added
- added tool to admin area to show list of bots
- tested with XenForo v2.1
- merge new bot array with core array rather than clobbering it
Same version, new addon_id.
If you already have v2.0.0 installed, there is no need to upgrade. There is no new functionality in v2.0.0a. New installations should use this v2.0.0a version to ensure compatibility with future releases.
Due to the change in addon_id, upgrading from v2.0.0 to v2.0.0a is not supported - but there is no data stored with this addon, so simply uninstalling v2.0.0 before installing v2.0.0a will be sufficient.