#intermittentbug
Live, measured metrics for the hashtag #intermittentbug from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #intermittentbug
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 #intermittentbug.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 23:05 UTCEverything below is measured over the latest 2 public posts (spanning ~25 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0.5
Used together with
Top of the latest posts
Latest round of #NetBSD10Beta tests on a Pi3: Summary for 931 test programs: 9424 passed test cases. 2 failed test cases. 59 expected failed test cases. 688 skipped test cases. One previously reported failure, and one new to me. Re-ran that
The filename_expansion #IntermittentBug succeeds when the scratch directory is an SD card, and times out after 5 minutes when the scratch directory is an outboard USB stick. Head scratcher, given the Pi 3 has a gigabyte of RAM and 4 cores.
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/intermittentbug