#relaynode
Live, measured metrics for the hashtag #relaynode from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #relaynode
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 22:29 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 22:29 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 22:29 UTCEverything below is measured over the latest 2 public posts (spanning ~14038 hours).
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 0.5
Top of the latest posts
Do we see here the first ever #RISCV based #TOR node running? I just provided a TOR node for the #onion network on one of my #VisionFive boards. This one currently runs on #Debian #Linux (will be switched to #FreeBSD soon). #onionrouting #p
Confused by Tor? Here’s the Simple Difference Between Relays, Bridges, and Exit Nodes (And Which You Should Run on Your LowEnd VPS) https://lowendbox.com/blog/confused-by-tor-heres-the-simple-difference-between-relays-bridges-and-exit-nodes
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/relaynode