#ampconf
Live, measured metrics for the hashtag #ampconf from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ampconf
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-09-30 02:29 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-09-30 02:29 UTCNo related tags with measured usage found for #ampconf.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-30 02:29 UTCEverything below is measured over the latest 4 public posts (spanning ~361 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 2
Used together with
No co-used tags in the sample.
Top of the latest posts
Even if you’re not interested in @[email protected], the link in this document ⤵️ by @[email protected] are well worth exploring. It’s mostly standards that were at least partly inspired by AMP. 👍 RT @[email protected] Doc wi
Awesome. Now AMP is lying to users via the URL. This is what scam sites do. --- RT @[email protected] AMP pages are beautiful, but links to AMP pages? Not so much ... Until today! Signed exchanges are here: now you can get instant loading
RT @[email protected] AMP Service Worker. Make your AMPs reliable and fast with one line. #AMPConf https://github.com/ampproject/amp-sw/blob/master/readme.md
#ampconf across platforms
every network with a public tag surfaceFollow #ampconf 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/ampconf