#swad
Live, measured metrics for the hashtag #swad from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #swad
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 · mastodon.online (Mastodon public tags API) · fetched 2026-10-15 23:11 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-10-15 23:11 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-15 23:11 UTCEverything below is measured over the latest 40 public posts (spanning ~1181 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (40)
Avg boosts / post: 0.7
Top of the latest posts
I need help. First the question: On #FreeBSD, with all ports built with #LibreSSL, can I somehow use the #clang #thread #sanitizer on a binary actually using LibreSSL and get sane output? What I now observe debugging #swad: - A version buil
Trying to further improve #swad, and as I'm still unhappy with the amount of memory needed .... Well, this little and special custom #allocator (only dealing with equally sized objects on a single thread and actively preventing #fragmentati
@zirias 👋 I would love to use a package of #swad
#swad across platforms
every network with a public tag surfaceFollow #swad 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.
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/swad