#sve2
Live, measured metrics for the hashtag #sve2 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #sve2
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 20:31 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 20:31 UTCNo related tags with measured usage found for #sve2.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 20:31 UTCEverything below is measured over the latest 9 public posts (spanning ~59125 hours).
Posting hours (UTC)
Languages: English (9)
Avg boosts / post: 0.2
Top of the latest posts
It would be very funny if a spec lawyering session on SVE2 accidentally uncovered a hypervisor bug in the worlds largest hypervisor vendor. #SVE #SVE2 #HPC #ARM
Resource: For those starting/looking at #SVE and #SVE2, @dougall made a superb instruction visualizer with presets for various Arm SVE enabled processors! Worth looking at to understanding what instructions are actually* doing under the hoo
What else? I do wonder if #MTE will be exposed this time around. Other questions? Do we *also* get real (read: full) #SVE and #SVE2 if so, how wide per core? There's also the possibility of #sme2 but that's probably a step too far
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/sve2