#mu4e
Live, measured metrics for the hashtag #mu4e from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #mu4e
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 07:34 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 07:34 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:34 UTCEverything below is measured over the latest 40 public posts (spanning ~9210 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (34) · French (3) · German (1) · Chinese (Taiwan) (1)
Avg boosts / post: 1.3
Top of the latest posts
For the first time in many years, I have less than 10 unread emails. 🎉 When I moved to #mu4e seven months ago, I was at 20,000! https://toot.aquilenet.fr/@civodul/114313643178812888
EDIT 2026-May-21: I just noticed that this function is clearly derived from one in @oantolin's config. Sorry I forgot! Did not mean to take credit. @csepp Here's a little thing I made to check for message body, subject line, and attachments
(setopt shr-use-colors nil) THIS SETTING COMPLETELY FIXES what has been by far my biggest annoyance with mu4e. Namely the ghastly clash of awful foreground and background colors in messages that can only be rendered as HTML. Thanks to Woute
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/mu4e