#x86_64_v3

Live, measured metrics for the hashtag #x86_64_v3 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #x86_64_v3

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.

$51.02/ year · 9-character #name
Claim #x86_64_v3 — $51.02/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
4
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 4
0.5
Avg reactions / post
Mastodon · last 4
—
Reddit posts / month
Reddit search
—
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-08-01 14:12 UTC
0
07-26
0
07-27
0
07-28
0
07-29
0
07-30
0
07-31
0
08-01

0 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-08-01 14:12 UTC
#x86_64v3
0 uses · 0 accounts / 7d

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-01 14:12 UTC

Everything below is measured over the latest 4 public posts (spanning ~13595 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: English (4)

Avg boosts / post: 0.3

Top of the latest posts

  • #Gentoo #Linux Begins Offering #x86-64-v3 Binary Packages Gentoo is joining the likes of Serpent OS, RHEL 10, Ubuntu and other Linux distributions that are optionally providing #x86_64_v3 packages or currently exploring the possibilities of

    Benjamin Carr, Ph.D. 👨🏻‍💻🧬@[email protected]♥ 2↻ 12024-02-23 00:37 UTCView post →

  • 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

    lymenzies@lymenzies♥ 0↻ 02025-08-07 04:30 UTCView post →

  • #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

    Benjamin Carr, Ph.D. 👨🏻‍💻🧬@[email protected]♥ 0↻ 02024-01-20 20:35 UTCView post →

#x86_64_v3 across platforms

every network with a public tag surface

Follow #x86_64_v3 straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.

X (Twitter) ↗Instagram ↗TikTok ↗Facebook ↗LinkedIn ↗YouTube ↗Threads ↗Bluesky ↗Mastodon ↗Reddit ↗Pinterest ↗Tumblr ↗

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_v3