#ortools
Live, measured metrics for the hashtag #ortools from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ortools
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 00:32 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 00:32 UTCNo related tags with measured usage found for #ortools.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 00:32 UTCEverything below is measured over the latest 19 public posts (spanning ~24443 hours).
Posting hours (UTC) — busiest: 07:00
Languages: English (15) · Russian (4)
Avg boosts / post: 1.1
Top of the latest posts
Finally getting back to the #constraintprogramming #ortools #scheduling/#routing #optimization problem I have a minimal working implementation of both a server and a selection of agents at various levels of realism. Two other #software peep
Solving the knapsack problem with @ApacheGroovy https://groovy.apache.org/blog/groovy-knapsack #groovylang #optimization #chocosolver #knapsack #ortools
This radar scheduling thing is dominated by a Knapsack Problem with a dash of Traveling Salesman to keep from wearing out hardware/looking dumb. I think I have a workable solution to each of these now. It took a little while to get the TSP
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/ortools