#l3build
Live, measured metrics for the hashtag #l3build from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #l3build
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-28 05:12 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-28 05:12 UTCNo related tags with measured usage found for #l3build.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 05:12 UTCEverything below is measured over the latest 7 public posts (spanning ~23058 hours).
Posting hours (UTC)
Languages: German (4) · English (3)
Avg boosts / post: 0.1
Top of the latest posts
Our presentation was followed by Ulrike Fischer asking herself if she broke something again… (Title was “Did I break something?” in German) Giving an overview of the mechanisms #l3build is providing für unit testing within #TeX/#TeXLaTeX fo
Weiter ging es mit „Habe ich was kaputt gemacht?“ Ulrike Fischer zeigte Methoden für Unit Tests bei #TeX und #TeXLaTeX. Durch das tagging-project sind da etwas speziellere Anforderungen dazu gekommen und sie präsentiert auch einen Test, der
Has anyone else made the experience that a bugtracker of a #TeXLaTeX project, declared via #l3build, is not shown on #CTAN? I followed the `l3build` package doc and specified it in the `uploadconfig` as `bugtracker`: https://codeberg.org/Cs
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/l3build