#timedomainreflectometer
Live, measured metrics for the hashtag #timedomainreflectometer from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #timedomainreflectometer
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 · mas.to (Mastodon public tags API) · fetched 2026-07-28 03:10 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-28 03:10 UTCNo related tags with measured usage found for #timedomainreflectometer.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-28 03:10 UTCEverything below is measured over the latest 3 public posts (spanning ~19406 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.3
Top of the latest posts
TDR For Auto Diagnostics Done On The Cheap https://fed.brid.gy/r/https://hackaday.com/2026/05/04/tdr-for-auto-diagnostics-done-on-the-cheap/
I never tried TDR (Time Domain Reflectometry) on the #nanovna_v2 before, but it turns out to be quite accurate! 😃 Once calibrated and configured with the right velocity factor (66% for RG-58), the length of the cable is seen as a major ref
Relatively recently, I got interested in time-domain reflectometry, which is essentially just sending a pulse down a cable and measuring the amount of time for its reflection to return. It's useful for testing long cables and finding where
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/timedomainreflectometer