#100daymapchallenge
Live, measured metrics for the hashtag #100daymapchallenge from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #100daymapchallenge
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 · mastodon.social (Mastodon public tags API) · fetched 2026-10-31 08:44 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-10-31 08:44 UTCNo related tags with measured usage found for #100daymapchallenge.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-31 08:44 UTCEverything below is measured over the latest 40 public posts (spanning ~824 hours).
Posting hours (UTC) — busiest: 17:00
Languages: English (40)
Avg boosts / post: 0.3
Top of the latest posts
Feb 9 → May 19, 2026. 100 consecutive days of GIS, 3D maps, WebGL, client work, experiments, and spatial storytelling. I collected the full campaign in an interactive calendar: https://maptheclouds.com/100-day-map-challenge/stats/ The campa
A personal note before Day 100 🗺️ I started this campaign as a test, not a plan. Open-source first, which pushed me into programming and browser-native maps. 🎮 The next chapter I want most: projects that genuinely help people. Maps as por
Day 96. Inner Fire 🔥 Inner Fire is my current attempt at treating global seismic activity less like static map data and more like a living planetary pulse unfolding through time. Built with React 19, React Three Fiber, GLSL, MapLibre, and
#100daymapchallenge across platforms
every network with a public tag surfaceFollow #100daymapchallenge straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/100daymapchallenge