#ConversationContainers
Live, measured metrics for the hashtag #ConversationContainers from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #conversationcontainers
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-29 19:05 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-10-29 19:05 UTCNo related tags with measured usage found for #conversationcontainers.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-29 19:05 UTCEverything below is measured over the latest 19 public posts (spanning ~16494 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (1)
Avg boosts / post: 1.7
Top of the latest posts
FEP-171b: Conversation Containers has been updated: https://codeberg.org/fediverse/fep/pulls/669 Notable changes: - Implementers are not required to publish the container collection anymore (although this is recommended). This part of the s
FEP-171b update: https://codeberg.org/fediverse/fep/pulls/454 Some clarifications, and an explanation of why FEP-fe34 authentication is important: >The processing of unauthenticated embedded activities is strongly discouraged. If such activ
"FEP-171b: Conversation Containers" finally has been published: https://codeberg.org/fediverse/fep/src/branch/main/fep/171b/fep-171b.md Conversation Containers are conceptually very similar to FEP-1b12: activities are sent to a conversation
#conversationcontainers across platforms
every network with a public tag surfaceFollow #conversationcontainers 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/conversationcontainers