#chatterbox
Live, measured metrics for the hashtag #chatterbox from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #chatterbox
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 06:04 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 06:04 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 06:04 UTCEverything below is measured over the latest 22 public posts (spanning ~62830 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (19) · Spanish (1) · German (1)
Avg boosts / post: 0.5
Top of the latest posts
I've been trying to design a new federated chat protocol, #Chatterbox, that improves on Matrix and XMPP and is simpler to use and implement than either. But, after a lot of work designing a WebSocket+Protobuf API, I've had to ask myself...
Seems like I'm not the only one that wants #Chatterbox's core features: https://sporks.space/2026/02/10/a-few-design-decisions-for-a-new-chat-platform/
Another thought re: Chatterbox and https://toot.nels.onl/@adam/115119481028785546 One of my main goals is ease of implementation, and that's the value that my current API isn't living up to. Maybe the solution is to keep the websocket and p
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/chatterbox