#heatplanning
Live, measured metrics for the hashtag #heatplanning from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #heatplanning
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-08-02 07:59 UTC1 uses by 1 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-08-02 07:59 UTCNo related tags with measured usage found for #heatplanning.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-02 07:59 UTCEverything below is measured over the latest 12 public posts (spanning ~29537 hours).
Posting hours (UTC) — busiest: 14:00
Languages: English (12)
Avg boosts / post: 0.3
Top of the latest posts
📢 This is our “heatshed” moment. Check out my new commentary with @SaraMeerow in the Journal of Urban Affairs' special issue on Extreme Heat in Cities. We argue that we are in a critical moment in history where heat mitigation, management,
I started a Substack on heat planning and governance! "The causes of extreme heat exceed political boundaries, and the solutions to address it must span sectors and levels of government. That is what a “heatshed” names. It’s the physical an
📢 Please reshare! Our NIHHIS Center for Heat Resilient Communities is now accepting applications for our first cohort to receive support to develop heat resilience roadmaps. https://www.noaa.gov/news-release/communities-can-now-apply-for-f
#heatplanning across platforms
every network with a public tag surfaceFollow #heatplanning straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/heatplanning