#38c3zigzag
Live, measured metrics for the hashtag #38c3zigzag from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #38c3zigzag
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-08-03 00:06 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-08-03 00:06 UTCNo related tags with measured usage found for #38c3zigzag.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-03 00:06 UTCEverything below is measured over the latest 26 public posts (spanning ~75 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (19) · German (5) · French (2)
Avg boosts / post: 0.4
Top of the latest posts
@elly carries a desktop PC on the stage for the presentation. I shouldn't be surprised, right? #38c3 #38c3zigzag
Use 1990s software, get 1990s bugs. Haven't seen memcopy vuls like this in a long time. Has anybody tried rewriting libarchive in Rust? #38c3 #38c3zigzag
In a surprising turn, the libarchive talk became relevant to @Ange interests. Nested/polyglot archives on Windows. #38c3zigzag #38c3
#38c3zigzag across platforms
every network with a public tag surfaceFollow #38c3zigzag 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/38c3zigzag