#openlocationcode
Live, measured metrics for the hashtag #openlocationcode from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #openlocationcode
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 20:34 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 20:34 UTCNo related tags with measured usage found for #openlocationcode.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 20:34 UTCEverything below is measured over the latest 9 public posts (spanning ~19325 hours).
Posting hours (UTC)
Languages: English (8) · German (1)
Avg boosts / post: 1
Top of the latest posts
Open Location Code (This post is being modified) https://bocops.app/eng/2025/02/open-location-code/
@lapingvino @factotum Btw, #normalization of #georeference|s is not trivial, because it requires techniques called #InstanceMatching. It's an entire field of ongoing research. A search for one of the #Berlin|s should be able to come up with
@lapingvino @factotum People who want to use exact #georeferencing in a posting should have a way to do so, for example for offline events or to describe #geospatial (or #marsian) features. 🌺 🏷️ #OLC #QTH #SemanticFediverse #ActivityPub #
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/openlocationcode