#GeoBlazor
Live, measured metrics for the hashtag #GeoBlazor from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #geoblazor
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-29 02:41 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-29 02:41 UTCNo related tags with measured usage found for #geoblazor.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 02:41 UTCEverything below is measured over the latest 40 public posts (spanning ~25071 hours).
Posting hours (UTC) — busiest: 18:00
Languages: English (40)
Avg boosts / post: 1.6
Top of the latest posts
HtmlRenderer class in #dotnet 8 will be extremely useful for #blazor libraries like #GeoBlazor. https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.components.web.htmlrenderer?view=aspnetcore-8.0
@damselfly this has to go through review, but should be available in the near future. #openstreetmap #arcgis #GeoBlazor #dotnet
Got a message from some folks publishing an app with #GeoBlazor to the iOS store. They ran into an issue with AoT limitations, opened a GH Issue and a PR all while I was traveling today. I love it when open source works like that.
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/geoblazor