#m2sync
Live, measured metrics for the hashtag #m2sync from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #m2sync
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-10-29 09:49 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-10-29 09:49 UTCNo related tags with measured usage found for #m2sync.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-29 09:49 UTCEverything below is measured over the latest 2 public posts (spanning ~1 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Used together with
Top of the latest posts
When using #m2sync, compared to #mbsync, you need to use "maildirpp:" instead of maildir "maildir:". Just though to mention since I was puzzling around this for few hours, and wondering why #notmuch finds everything, and aerc finds nothing.
I found a modern actively updated alternative for #isync (or #mbsync): #m2sync It is part of #vomit project: https://sr.ht/~bitfehler/vomit/ Compared to the complexity of ~/.mbsyncrc, my config is now dead simple: cat .config/vomit/config.t
#m2sync across platforms
every network with a public tag surfaceFollow #m2sync 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/m2sync