News for hackers. Stuff that matters.

A comment on Matomo-org/device-detector: Universal Device Detection library from User Agent.

Re:Matomo-org/device-detector: Universal Device Detection li... by qingcharles on Wednesday November 27, 2024 @09:28PM (#42261863)
I have a bot I wrote to help me with various web tasks that are too tedious manually. I just tested it against this and it says "isbot: false".

edit: looks like it only detects bots that overtly identify themselves as bots, e.g. Googlebot -- it's designed to identify clients, not as some sort of security device

[ Parent | on HN ]
Re:Matomo-org/device-detector: Universal Device Detection li... by riiii on Thursday November 28, 2024 @03:26AM (#42263574)
That flag should be called isKnownBot.
[ Parent | on HN ]
Re:Matomo-org/device-detector: Universal Device Detection li... by cbolat on Thursday November 28, 2024 @07:14AM (#42264673)
It has a misleading name, it should be just a user-agent detector, as one cannot identify devices by just looking at user-agent header.
[ Parent | on HN ]
Re:Matomo-org/device-detector: Universal Device Detection li... by mrweasel on Thursday November 28, 2024 @10:28AM (#42265904)
The worst bot normally doesn't identify themselves as bots.

A really useful flag would be "isAIBot" so you can tell them to f-off. A colleague returned from SRECon and had been asking around in regards to bots from AI companies and it's getting ridicules. AI companies are just hammering sites left and right, to the point where some are hitting the limits on their deals with hosting companies and transit providers.

And you can't filter them out, because their running on AWS, Azure or GCP IPs and aren't identifying themselves properly.

[ Parent | on HN ]
Re:Matomo-org/device-detector: Universal Device Detection li... by cynicalsecurity on Thursday November 28, 2024 @02:19PM (#42267880)
Why allow free and unrestricted connections from hosting companies in the first place?
[ Parent | on HN ]