#FireworksFail
Live, measured metrics for the hashtag #FireworksFail from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fireworksfail
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-07-27 23:05 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-07-27 23:05 UTCNo related tags with measured usage found for #fireworksfail.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 23:05 UTCEverything below is measured over the latest 4 public posts (spanning ~0.1 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 1.5
Top of the latest posts
I used to have a lot more Fireworks Fails, back when I mostly shot fireworks freehand with the automatic settings. Now I do it much more conventionally and sensibly with a tripod, so things usually look sort of like they should. That's most
One more good Fireworks Fail from Friday night. This one is genuinely beautiful. This came from the Canon 90D. I didn't have the head on the tripod screwed down tightly enough and it suddenly tilted back mid-exposure. July 3, 2026. Wolverin
This was a fun fireworks fail. I accidentally knocked my iPhone off the porch rail while it was shooting on night mode. July 3, 2026. Wolverine Lake, Michigan. #photography #fireworks #michigan #summer #art #FireworksFail
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/fireworksfail