#corrigendum
Live, measured metrics for the hashtag #corrigendum from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #corrigendum
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.social (Mastodon public tags API) · fetched 2026-10-10 02:33 UTCNo measured public usage for #corrigendum in the last 7 days. That is a real result, and a good one to know: this hashtag is wide open right now. We show a dash before we ever show a made-up number. Browse the trending index for tags with live measurements.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-10-10 02:33 UTCNo related tags with measured usage found for #corrigendum.
Live pulse
measured · Mastodon tag timeline · fetched 2026-10-10 02:33 UTCNo recent public posts found for #corrigendum on Mastodon. Nothing measured, so nothing shown.
What “corrigendum” means
Wiktionary · Wikipediacorrigendum/ˌkɒɹ.ɪˈdʒɛn.dəm/
- nounAn error that is to be corrected in a printed work after publication.
An erratum or corrigendum is a correction of a published text. Generally, publishers issue an erratum for a production error and a corrigendum for an author's error. It is usually bound into the back of a book, but for a single error a slip of paper detailing a corrigendum may be bound in before or after the page on which the error appears. An erratum may also be issued shortly after its original text is published.
“Erratum” on Wikipedia (CC BY-SA) →#corrigendum across platforms
every network with a public tag surfaceFollow #corrigendum 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/corrigendum