#githubfail
Live, measured metrics for the hashtag #githubfail from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #githubfail
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-30 04:10 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-30 04:10 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 04:10 UTCEverything below is measured over the latest 5 public posts (spanning ~2529 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0
Top of the latest posts
Oh no! 😱 Another day, another GitHub fiasco. Someone apparently fell asleep at the security wheel 🚫🔒, and now we're all supposed to panic because "Mantine-datatable" got a time-out. Maybe next time, try locking the door before you leave
A #githubfail for @wezm—if you've turned off PRs for a repo, when you get a dependabot notification it just 404s, since it can't open a PR. There's a perfectly good security tab it could link to.
I click the Commits tab on a PR. The blue pjax loading bar starts its slow, erratic crawl across the top of the page. It gets closer and closer to the end, the page remaining unchanged the whole time. It reaches the end. Nothing happens. No
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/githubfail