#tbeam
Live, measured metrics for the hashtag #tbeam from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tbeam
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-09-15 16:46 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-09-15 16:46 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-09-15 16:46 UTCEverything below is measured over the latest 40 public posts (spanning ~23564 hours).
Posting hours (UTC) — busiest: 21:00
Languages: English (37) · German (2) · Ukrainian (1)
Avg boosts / post: 0.8
Top of the latest posts
Like I mentioned, I don't know a lot about #MeshNetworks, but I'd love to know what others think of the #MeshTastic systems. This seems to be a pretty up-to-date guide on how to set up a Mesh network (there wasn't a date on the piece, but t
Working toward running #microReticulum natively on the LilyGO T-Beam SUPREME (ESP32-S3 + SX1262). Hardware exercises complete (GPS, OLED, SD) and basic LoRa ping-pong via RadioLib. Next: implement a proper Reticulum LoRa interface layer for
Published a new Reticulum testing note: simulating mesh-network distance in the lab by using software “blocking pairs” between nearby T-Beams. This lets a desktop test force packets through intermediate transport nodes instead of requiring
#tbeam across platforms
every network with a public tag surfaceFollow #tbeam 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/tbeam