#microsoftword365
Live, measured metrics for the hashtag #microsoftword365 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #microsoftword365
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:43 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:43 UTCNo related tags with measured usage found for #microsoftword365.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:43 UTCEverything below is measured over the latest 2 public posts (spanning ~7629 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0.5
Used together with
Top of the latest posts
Strange thing I'm noticing in #JFW2026 it's happened twice this week. When in #MicrosoftWord365 JFW isn't reading properly. It's like entire sections of text are skipped over. But if I use Control A to highlight in full then I can read prop
I always say I'm never afraid to say I was wrong. And so apparently I am wrong and @brian_hartgen is right. I've finally been hit with a bug in #JAWS2025 and it's a bad one. When in #MicrosoftWord365 if you navigate to the ribbon, mailings
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/microsoftword365