matomo-org / matomo-org/device-detector

Bot types

Open
#7,489 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
3.5k
Forks
513
Avg merge
1d 21h
Merged PRs (30d)
11

Description

Variable for bots `$categories` has some ambiguous types:

- `Feed Fetcher`, `Feed Parser`, `Feed Reader` - what's the difference, really?
- `Read-it-later Service` is used only for 2 items both for 1 thing: https://getpocket.com/pocketparser_ua. At the same time description on this page clearly says `crawling`, so should this not be `Crawler`?
- `Search tools` is used only for 1 item: http://www.shopwiki.com/w/Help:Bot. Again, description clearly states, that this is a crawler, so should this not be `Crawler`?
- How does `Security search bot` differ from `Security Checker`?
- How does `Service bot` differ from `Service Agent`?
- And probably the biggest of it all: what's the difference of `Search bot` from `Crawler`? I mean, crawling is done by search bots, so this seems to be the same thing.

I am fine with creating PR to harmonize these things a bit, but I think this warrants a proper discussion first.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the $categories variable and the entries for Feed Fetcher, Feed Parser, Feed Reader, Read-it-later Service, Search tools, Security search bot, Security Checker, Service bot, Service Agent, Search bot, and Crawler. Compare their descriptions and usage, then seek agreement on the taxonomy before changing anything. Done means the bot categories are consistently defined and harmonized.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.