#x86_64_v2
Live, measured metrics for the hashtag #x86_64_v2 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #x86_64_v2
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-31 13:38 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-31 13:38 UTCNo related tags with measured usage found for #x86_64_v2.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-31 13:38 UTCEverything below is measured over the latest 2 public posts (spanning ~13544 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Top of the latest posts
I've been going around to all my little x64 systems running /lib64/ld-linux-x86-64.so.2 --help to see what Intel #microarchitecture they support. So far, everything is either #x86_64_v2 or #x86_64_v3 Not too much of a surprise, given the ag
#RedHat Evaluating x86-64-v3 Requirement For #RHEL10 #RHEL 9 requires #x86_64_v2 while for Red Hat #EnterpriseLinux 10 they are looking at upping things to #x86_64_v3 that would basically mandate #Intel and #AMD #CPU with #AVX/#AVX2 support
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/x86_64_v2