Closed stevenvachon closed 8 years ago
This module works by matching user agent with bot list. User agents are only used for testing purpose so not sure why would we need to do that?
Bot lists change.
bot list updated #3
I am open to changes, if you want to provide that functionality it would be great
It would undo some of the additions made in #3, though, as I would probably use only user-agents.org
Hey heads up that user-agents.org is really outdated. I mentioned over in the bot-detector module issue, which uses user-agents.org exclusively, that it seems that many of user-agents.org ua strings haven't been updated in 10 years.
Some other sources to consider:
For a script performing automatic updates, any sources would have to be trusted to be accurate both now and in the future (ie. I spent yesterday picking through ua strings for #3 and found a decent amount inaccuracies in sources). So I think a 100% automated npm update script puts too much trust in sources, perhaps a good middleground be would to:
If someone writes such a sources updating script, I'd be willing to take on step 2 above as a maintainer and run it weekly because isbot is going to be an integral part of an open-source bot detection project I'm working on and will be releasing soon.
If someone writes such a script that update browser.txt and crawlers.txt we can use ci service to run tests automatically once a day
using something like http://www.user-agents.org/