#towncrier
Live, measured metrics for the hashtag #towncrier from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #towncrier
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-31 10:56 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-31 10:56 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-31 10:56 UTCEverything below is measured over the latest 12 public posts (spanning ~53809 hours).
Posting hours (UTC) — busiest: 02:00
Languages: English (11) · Portuguese (1)
Avg boosts / post: 1.5
Top of the latest posts
Practically, I find it very helpful to write the change log item as an update to the change log document, included *as separately written documentation*, one change among others included in the same merge request. Consider it like updating
Agreed @webaware, it is a clear sign that the release was made with no user-facing description of the changes. If you don't already have the user-facing description of the change ready, it's not ready to commit to version control, and certa
Been playing around with #towncrier for the past couple of days. I like its approach to creating & updating changelogs(plus its support for both .md & .rst output) Between its clear tutorial and referencing pipx & pytest's usage of the pack
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/towncrier