#remoteradio
Live, measured metrics for the hashtag #remoteradio from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #remoteradio
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-31 04:38 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-31 04:38 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-31 04:38 UTCEverything below is measured over the latest 12 public posts (spanning ~21490 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (12)
Avg boosts / post: 0.5
Top of the latest posts
I have built a simple CW remote keyer in python that works very good in this early stage. Its inspired by #DL4YHF Remote CW keyer that can be found here - https://www.qsl.net/dl4yhf/Remote_CW_Keyer/Remote_CW_Keyer.htm Example video of me ru
@dj3ei @KZ4LN @victor_59 I have now tested output via a raspberry pi4 over wifi. Sidetone is on the sender side. Sorry for the low volume... #MorseCode #CW #RemoteRadio #opensource #Hamradio
Update (3/3) **Duration + Timestamps (version2)** Sending an "A" at 25 wpm T+0ms: Send packet [seq=1, DOWN, 48ms, ts=0ms] # Dit starts T+48ms: Send packet [seq=2, UP, 48ms, ts=48ms] # Dit ends T+96ms: Send packet [seq=3, DOWN, 144ms, ts=96m
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/remoteradio