#mudblazor
Live, measured metrics for the hashtag #mudblazor from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #mudblazor
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-28 03: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-28 03:30 UTCNo related tags with measured usage found for #mudblazor.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 03:30 UTCEverything below is measured over the latest 16 public posts (spanning ~20279 hours).
Posting hours (UTC) — busiest: 17:00
Languages: English (15) · German (1)
Avg boosts / post: 1.5
Top of the latest posts
Just upgraded Damselfly to #MudBlazor 7. Took about 20 minutes. Great upgrade! #blazor
If you are using #mudblazor for your #dotnet #blazor project there is a pretty meaty update planned. With it comes a hefty sum of breaking changes. The team has provided an awesome migration guide though: https://github.com/MudBlazor/MudBla
This release brings multi-level grouping in MudDataGrid and several other improvements and fixes. If you noticed the regression in scrollable dialogs, it is fixed in this release as well: https://github.com/MudBlazor/MudBlazor/releases/tag/
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/mudblazor