#bridgyfed
Live, measured metrics for the hashtag #bridgyfed from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #bridgyfed
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 02:31 UTC2 uses by 1 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 02:31 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 02:31 UTCEverything below is measured over the latest 40 public posts (spanning ~1509 hours).
Posting hours (UTC) — busiest: 22:00
Languages: English (21) · Japanese (10) · Portuguese (3) · Spanish (2) · German (1) · Italian (1)
Avg boosts / post: 0.5
Top of the latest posts
Some of you remember the 2024 Bridgy Fed consent dust‑up; others (like me) arrived later or were hanging out in other corners of the fediverse. We just published a piece that tries to lay out the whole thing in one place: how AT Protocol an
@baileytownsend hello ! I'm the one asking everyone to enable the #bridgyfed even on secondary accounts, because my ideal world is to discuss with people regardless of where they come from, and double accounts break the flow 🙂
RE: https://chaos.social/@joergi/116852270118901982 EDIT: Oops, nope, this is actually for migrating your bridged account on the other network *out* of Bridgy. I misunderstood the purpose of this feature, and Bridgy won't have any control o
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/bridgyfed