#janssfire
Live, measured metrics for the hashtag #janssfire from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #janssfire
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 18:35 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 18:35 UTCNo related tags with measured usage found for #janssfire.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 18:35 UTCEverything below is measured over the latest 12 public posts (spanning ~0.9 hours).
Posting hours (UTC) — busiest: 23:00
Languages: English (12)
Avg boosts / post: 1.2
Used together with
Top of the latest posts
Fire holding at 2 acres, Forward Progress Stopped (FPS). All units committed 3-4 hours 10/21/25 1650PT (my last update) #JanssFire #VenturaCounty
Control objectives: S of Westlake, E of Janss W of Bridgegate N of Potrero. 10/21/25 1645PT #JanssFire #VenturaCounty
Request for 2 addl Type 3's for contingency. 10/21/25 1640PT #JanssFire #VenturaCounty
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/janssfire