#EarthquakeSF
Live, measured metrics for the hashtag #EarthquakeSF from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #earthquakesf
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 · mastodon.social (Mastodon public tags API) · fetched 2026-11-13 17:00 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-11-13 17:00 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-11-13 17:00 UTCEverything below is measured over the latest 2 public posts (spanning ~476 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 1
Top of the latest posts
Great thing on @Mastodon right now is you can go first to start some new hashtags, apparently use them here more for cross-server searches. Lots already in use. Def want will more here, adding #SFQuake #Books #PeaceProcessing #SanFrancisco
@MBridegam @sanfrancisco @sfchronicle so far there’s too long a delay between tag and post. I think for earthquake speed will need to stick with hashtags (and pending various server capacities, that will not be anywhere near as instantaneou
#earthquakesf across platforms
every network with a public tag surfaceFollow #earthquakesf 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/earthquakesf