#gnss
Live, measured metrics for the hashtag #gnss from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #gnss
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 05:18 UTC1 uses by 1 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 05:18 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:18 UTCEverything below is measured over the latest 40 public posts (spanning ~1221 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (24) · German (8) · Russian (3) · French (2) · Chinese (Taiwan) (2) · Italian (1)
Avg boosts / post: 2.1
Top of the latest posts
Great paper on wide-area transient interference,from a space-based source causing up to 10-dB GNSS degradation across Europe since 2019 in the important L1 band, from Russian early warning satellites in Molniya (“lightning”) orbits. Cosmos
🛰️ It's here: native NTRIP support in QField 4.2. Sub-centimeter accuracy with no third-party app. Connect an RTK correction-capable GNSS device over Bluetooth, BLE or TCP, enter your NTRIP caster details in the positioning panel, and corr
A timing investigation for seven T-Beams: their external RTC preserves whole seconds, but cannot establish millisecond event order across units. I added GNSS PPS capture plus ESP32 monotonic interpolation, compared the resulting disciplined
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/gnss