#upri
Live, measured metrics for the hashtag #upri from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #upri
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-28 20:22 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-28 20:22 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 20:22 UTCEverything below is measured over the latest 5 public posts (spanning ~14172 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 1
Top of the latest posts
NOTE 1. The flood hazard data has invalid geometries/features. You can resolve this by fixing the geometries (takes a long time) or simply disabling the Invalid features filtering in QGIS processing settings. 2. Some areas have no flood haz
... 3. Generate centroids from the output of #2 (either using the Centroids algorithm or Geometry generators). 4. To speed up and automate the process, I created a model that runs steps 1-3 above. 5. Style the output of 3 using: marker = he
PROCESS 1. Use the "Sort" algorithm to create an ordered version of the flood hazard layer such that the features with high hazard level (3) will always be the first feature that will be matched in #2 below. 2. Run a "Join attributes by Loc
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/upri