#fldigi
Live, measured metrics for the hashtag #fldigi from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fldigi
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-28 03:41 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-28 03:41 UTCNo related tags with measured usage found for #fldigi.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 03:41 UTCEverything below is measured over the latest 40 public posts (spanning ~18356 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (37) · German (2) · Catalan (1)
Avg boosts / post: 0.6
Top of the latest posts
Heard about the digital #hamradio bulletin of @C from @dd0ul and tried to receive it in JO62 today. Forwarded the audio of my #OpenWebRX into #fldigi and successfully decoded the MFSK-32 signal. #Amateurfunk
@KC8JC feeling the same but not limited to #WSJTX but also #JS8call and #Fldigi. As I have no clue of C/C++, I would have do a complete rewrite. That is also beyond my capabilities. Somebody is porting Direwolf to Golang. At least that is s
#HamChallenge Week 20: Decode the RTTY transmission of DWD on 10101 kHz I just decoded this weather report using #fldigi: GENERAL SYNOPTIC SITUATION: A LOW 1013 IS MOVING FROM BELARUS TO EASTERN UKRAINE. A HIGH 1028 OVER THE CZECH REPUBLIC
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/fldigi