#intelprocessorbug
Live, measured metrics for the hashtag #intelprocessorbug from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #intelprocessorbug
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 10:02 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 10:02 UTCNo related tags with measured usage found for #intelprocessorbug.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 10:02 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 5
Used together with
Top of the latest posts
John Carmack retweeted the following, yesterday: “I wonder why people haven't yet deduced that all CPUs have like 26 bugs at least as serious as this Intel one, it's just that nobody has found them yet.” https://twitter.com/Jonathan_Blow/st
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/intelprocessorbug