#mbsync
Live, measured metrics for the hashtag #mbsync from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #mbsync
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 08:30 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-27 08:30 UTCNo related tags with measured usage found for #mbsync.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:30 UTCEverything below is measured over the latest 40 public posts (spanning ~19745 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (40)
Avg boosts / post: 0.1
Top of the latest posts
For quite some time I have sporadically run #mbsync configured to pull several IMAP accounts and it indeed brings in emails. BUT: - #maildir format is weird. What's with the cur/new/tmp structure? - why the heck is the hostname in the filen
OK, I'm going to give it another try to make #emacs, #msmtp, #mbsync, #notmuch work for taming email. I'm looking (sternly 😡 ) at you, gmail forced down my throat by my <insert-employer-entity-here>... My ideal setup would likely be simple
PSA: I don't know who else needs to know this but if you're trying to get #neomutt working in #ubuntu but #mbsync is failing then take a look at #apparmor. It took me about an hour to figure this out & another hour to find a fix (found a gr
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/mbsync