#TinyCC
Live, measured metrics for the hashtag #TinyCC from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tinycc
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 21:02 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 21:02 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 21:02 UTCEverything below is measured over the latest 19 public posts (spanning ~44971 hours).
Posting hours (UTC) — busiest: 20:00
Languages: English (15) · French (2) · Italian (1) · Russian (1)
Avg boosts / post: 2.5
Top of the latest posts
@ekaitz_zarraga and I have finally bootstrapped #TinyCC on #RISCV starting from GNU #Mes and #MesCC (and eventually tiny #hex0 binary if you go further back). The binary that we have built is self-hosting and can build itself, though perhap
@janneke @aziz @fsf @fsfe @reproducible_builds @ekaitz_zarraga Indeed! Right now we can bootstrap all the way from #hex0 to #Mes, then use #MesCC to build very first build of #tinycc (we can call it mes-tcc). mes-tcc can then build the next
Spent part of my #RechageDay at #AMD looking at bootstrapping #TinyCC 0.9.26 from #GNUMes on #x86_64 architecture. And thanks to #Mes mantainer @janneke for his help with debugging various issues. We can now build initial #tcc binary and it
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/tinycc