#x86_64
Live, measured metrics for the hashtag #x86_64 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #x86_64
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 06:22 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 06:22 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 06:22 UTCEverything below is measured over the latest 40 public posts (spanning ~8080 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (34) · French (1) · Russian (1) · Chinese (Taiwan) (1) · Japanese (1) · Spanish (1)
Avg boosts / post: 0.6
Top of the latest posts
#openSUSE Leap 16.0 public cloud images are now available for both #x86_64 and #Arm64. Launch it today via Compute Engine and deploy your workloads on a stable #Linux distribution. https://sysadmin-journal.com/opensuse-leap-16-0-is-now-avai
I’m trying to write an OS in #swift I’ve managed but have since deleted everything to start a fresh. Few questions I need answered: 1. #x86_64 #RISCV or #arm64 2. Standard or embedded 3. Mix of C and Swift or Pure Swift 4. String type imple
The start of JITDUMP support for MoarVM (#rakulang language virtual machine) wasn't terribly difficult. Still some stuff to figure out, though. #pldev #x86_64
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