#autoconfig
Live, measured metrics for the hashtag #autoconfig from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #autoconfig
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 · mas.to (Mastodon public tags API) · fetched 2026-07-27 20:10 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-27 20:10 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 20:10 UTCEverything below is measured over the latest 6 public posts (spanning ~51081 hours).
Posting hours (UTC)
Languages: English (4) · Russian (1) · German (1)
Avg boosts / post: 1
Top of the latest posts
@SnoopJ @glyph @tante #PegDHCP was peak #Autoconfig!
Our sincere apologies regarding the recent Nettify incident. #Thunderbird #Mozilla #TechNews #TechUpdates #Nettify #Autoconfig https://officialaptivi.wordpress.com/2025/03/20/nettifys-thunderbird-autoconfig-incident/
Nettify’s Thunderbird Autoconfig Incident Addresstigator was unveiled on January 4th, 2022, with one idea in mind: to easily allow C# programs to determine the server configuration from just one e-mail address using Thunderbird’s Autoconfig
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/autoconfig