#coversations
Live, measured metrics for the hashtag #coversations from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #coversations
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-11-08 00:33 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-11-08 00:33 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-11-08 00:33 UTCEverything below is measured over the latest 2 public posts (spanning ~14453 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 1
Used together with
Top of the latest posts
RE: https://mastodon.social/@Valdemir_sales/117394812552311649 Resolvido. Em menos de um dia estudei o protocolo #XMPP ,analisei os clientes(aplicativos), fiz os testes, entendi a lógica de chaves da criptografia OMEMO Fiquei mais de 02:40:
@maple I'm using Gajim 1.9.5 from flatpak, and my SSL cert hasn't expired for my upload.example.com domain. certbot auto-renews it. #Coversations and #Dino both send attachments just fine; just not #Gajim. I agree with you as to "no thanks"
#coversations across platforms
every network with a public tag surfaceFollow #coversations 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/coversations