Mock

https://prtksxna.github.io/wmf-cu-prototype/compare.html (source)

@Niharika ^^^^ for Description.

@Prtksxna: I'd add a minor feature - a "Proxy/VPN check" link - after "Tor check" (pull request): <a href="https://www.ipqualityscore.com/free-ip-lookup-proxy-vpn-test/lookup/<?=$IP ?>">Proxy/VPN check</a>

For geolocation (no link in prototype) I prefer to use "https://www.iplocation.net/?query=<?=$IP ?>"
which presents data from 3 sources (that often differ). These include https://whatismyipaddress.com/ip/1.1.1.1 and https://db-ip.com/1.1.1.1 currently used on IP contributions pages
Note: one more useful alternative (50/day free requests only): https://www.ip2location.com/demo/1.1.1.1

A more substantive task.
Add 3 columns: Subnet (name and ip range of the subnetwork), Geolocation (closest city, generally), Proxy/VPN (reported/detected proxies)
This would greatly increase the efficiency of recognizing IPs from around the world (VPN users), dynamic ips on the same subnet, open proxies/free VPNs, etc.

Edits are grouped by IP+UA on the mockup, summing edit count. Edits from the same subnet should be grouped together as well. This will collapse potentially dozens of IPs for dynamic IP users.

The subnet (Whois), geolocation, proxy info is aggregated from on-site databases or online services.
The task to develop the backend is: T174553: Create a mechanism that allows fetching geolocation and subnet data for IP addresses

From the description:

@Prtksxna What happens when the user gets rid of all the rows in the table with the filters?

If this, happens we should leave the filters box open and show a notice. The notice should let them know what has happened with an option to remove all filters. You can see an example here - https://prtksxna.github.io/wmf-cu-prototype/empty.html

@Prtksxna We'd need to have a loading animation for when the results are being filtered/reloaded.

For the loading animation we'll use the same one as RecentChanges (and other places on the site). You can find the code in Volker's codepen - https://codepen.io/Volker_E/pen/yqNXMe

I have added an example in https://prtksxna.github.io/wmf-cu-prototype/index.html. Clicking submit now shows the loading indicator for two seconds before loading the table.

Notes from the estimation meeting

• We want to start with server side pagination and iterate upon it later, depending on whether we need client side pagination or not.
• Highlights, sort and filters would stay sticky across the paginated tabs (is that the right word?)
• We decided to go with Option 2 in the task description as it makes sense to filter/highlight all data together. We will need a good way to visually distinguish users and IPs the user explicitly queried for.

Tickets we want to split this into:

1. Getting the data, sorting and pagination - 8
   • This includes getting the requested data from the server with the sort options selected by the user. Sorting can be done by username, IP and user-agent. No sorting by activity.
2. Display the data - 3
   • This involves displaying the data in the table. Assuming no filters or highlights exist at this point.
   • Records sorted by the options pre-selected by the user. If no options are previously selected, they are grouped by the usernames and IPs requested by user. If a username and an IP were both looked up, we club the record with the username.
3. Building the filters and filtering
   • This task is to build the filtering UI and doing the actual filtering in the UI. Works across paginated tabs.
4. Build the sticky highlights
   • This task is to build the sticky highlighting UI. Sticky across paginated tabs.
5. Adding the new data records
   • This task is to add the new records to the table when a user clicks the 3 other IPs or 4 other users links (or however the design wants to make that work).

CC to this task too..
T236225#5701262

@Rxy The AHT team has taken on rewriting and redesigning CheckUser as part of the general strategy around this area. This means that we are *heavily* editing the code, and the plan is to replace the current CheckUser special page with the new one that we're building.