#codesprint19
Live, measured metrics for the hashtag #codesprint19 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #codesprint19
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 08:02 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 08:02 UTCNo related tags with measured usage found for #codesprint19.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:02 UTCEverything below is measured over the latest 13 public posts (spanning ~405 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (13)
Avg boosts / post: 0.8
Top of the latest posts
We have started the #OGCAPI #CODESPRINT19 in brussels & #discord , with presentations about different #OGC #standards that support creating web maps
The new contribution from @IvanSanchez to #pygeoapi enables the web map client to preview #OGCAPI coverages, with multiple projections! 👏 #CODESPRINT19 #standards #OSGEO #FOSS4g
Now you can publish OGC API Tiles with #pygeoapi using: #elasticsearch, #pg_tileserv, mapbox tiles in disk, or other formats you like 😀 #OGCAPI #CODESPRINT19 There is no excuse anymore. for not being #OGC compliant, while using vector tile
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/codesprint19