#externallydisabled
Live, measured metrics for the hashtag #externallydisabled from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #externallydisabled
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-28 05:07 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-28 05:07 UTCNo related tags with measured usage found for #externallydisabled.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 05:07 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 0
Used together with
No co-used tags in the sample.
Top of the latest posts
@zacky I've met this exact problem before. My solution was to actually reflect `disabled`, but having another internal field, e.g. `#externallyDisabled`, that tracks what comes from `formDisabledCallback`. So `this.disabled || this.#externa
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/externallydisabled