#svid
Live, measured metrics for the hashtag #svid from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #svid
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 13:01 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 13:01 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:01 UTCEverything below is measured over the latest 3 public posts (spanning ~7469 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.7
Top of the latest posts
@bytebro This is not a conflict of standards. None of those are standardized. Indeed, this is what you get for using all of these non-standard things instead of the thing that *is* standardized: pkgadd from magtape, per the System 5 Interfa
@cks @whitequark It's interesting comparing Usenet of 1993 to Hacker News of today. Some questions are perennial, it seems: "But what use is malloc(0)?" followed by a discussion of people rolling their own Pascal-like strings. "Why unique?"
@cks @whitequark Back in 1993, #AIX was the example that people gave of a C library where malloc(0) returned NULL. https://groups.google.com/g/comp.unix.aix/c/lstmVEcmD2Q/m/wRsWt_Tnw1UJ Most of the C libraries that I touched back then eithe
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/svid