views.toolforge.org/tools
wikitech-l
May 21, 2026 11.15 PM : There is also a system you can use at https://toolviews.toolforge.org/api/ which attempts to count 2xx status responses (”hits”) for all tools by parsing the access logs generated at the Toolforge reverse proxy service. That system does not currently have a nice UI, but it does have data going back to at least 2019 and does not require inserting tracking tokens in your pages.
May 21, 2026 11.46 PM : The toolviews API is cool. Have done a small attempt couple of months ago during a workshop for visulize the views based on this API at https://views.toolforge.org/tools/
Alright. This is actually one of my biggest wishes in the Toolforge ecosystem. I want to see the stats of all of my deployed tools over there.
Now, I can finally see them.
So, sorted by popularity, it’s wdlite, wd-nearbyItem, wdquery, and wplmon.
Meanwhile, for myself, I frequently use wdlite first, then either wplmon or wdquery.
wdlite is useful for quickly grasping the current “depth and breadth” of a wikidata item. Sometimes, you’ll get more interesting results by searching wikidata items through it instead of using a search engine query. Just try it yourself.
I frequently use wplmon to study the “behavioral aspects” of certain wikipedians.
wdquery is basically a simpler alternative to the wikidata query qervice, based on the recently deployed GraphQL API.
I rarely touch wd-nearbyItem myself because now I usually use Altiliunium LocationPad to manage my own dataset of coordinates. So, I don’t rely on Wikidata anymore to store my “personal” collection of cherished coordinate data.