#bugstories
Live, measured metrics for the hashtag #bugstories from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #bugstories
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-27 20:07 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-27 20:07 UTCNo related tags with measured usage found for #bugstories.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 20:07 UTCEverything below is measured over the latest 10 public posts (spanning ~62541 hours).
Posting hours (UTC)
Languages: English (10)
Avg boosts / post: 3.2
Top of the latest posts
I noticed a bug in our binutils port that had been generating semi-randomly broken branch relaxation trampolines for decades. Why did it take so long to notice this code generation bug? The branch has to reach farther than +-32MB for the br
You might be interested to learn how I tracked this bug down. In short, I was quite lucky. I was working on adding HTTP/3 support to a WebKit-based browser. Suddenly, the browser build began to crash at exit. Closer inspection revealed that
As it happens, we still use CVS in our operating system project (there are reasons for doing this, but migration to git would indeed make sense). While working on our project, we occasionally have to do a full checkout of the whole codebase
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/bugstories