#diplexer
Live, measured metrics for the hashtag #diplexer from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #diplexer
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 · mastodon.social (Mastodon public tags API) · fetched 2026-10-10 22:07 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-10-10 22:07 UTCNo related tags with measured usage found for #diplexer.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-10 22:07 UTCEverything below is measured over the latest 2 public posts (spanning ~0.2 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0.5
Top of the latest posts
Passive Diplexer Makes One Antenna Act Like Two https://hackaday.com/2024/05/22/passive-diplexer-makes-one-antenna-act-like-two/ #automaticpacketreportingsystem #amateurradio #RadioHacks #diplexer #duplexer #discone #filter #APRS #LoRa #ham
Passive Diplexer Makes One Antenna Act Like Two - Stay in the amateur radio hobby long enough and you might end up with quite a coll... - https://hackaday.com/2024/05/22/passive-diplexer-makes-one-antenna-act-like-two/ #automaticpacketrepor
What “diplexer” means
WikipediaA diplexer is a passive device that implements frequency-domain multiplexing. Two ports are multiplexed onto a third port. The signals on ports L and H occupy disjoint frequency bands. Consequently, the signals on L and H can coexist on port S without interfering with each other.
“Diplexer” on Wikipedia (CC BY-SA) →#diplexer across platforms
every network with a public tag surfaceFollow #diplexer straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/diplexer