To help checkusers better understand User Agent strings and be able to decipher patterns faster, Anti-Harassment would like to parse User Agent strings in CheckUser (See T175587).
From our research, it seems the best way to do this is with the whichbrowser/parser library (unless another alternative exists that we are unaware of).
We would like to add this to the extension and to production after an approved security review.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T139810 RFC: Overhaul the CheckUser extension | |||
| Open | • Niharika | T236225 [Epic] CheckUser 2.0 Improvements | |||
| Open | • Niharika | T237593 [Epic] CheckUser 2.0: Compare | |||
| Open | None | T175587 Add a user-agent parser to CheckUser | |||
| Resolved | Reedy | T239259 Security Review for whichbrowser/parser |
I note, but not necessarily a blocker, that the Developer(s) don't seem very active based on https://github.com/WhichBrowser/Parser-PHP and the issues/pull requests. Handful of bugs and reports etc that have gone without response to for months