#garlicRouting
Live, measured metrics for the hashtag #garlicRouting from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #garlicrouting
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 23:53 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 23:53 UTCNo related tags with measured usage found for #garlicrouting.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 23:53 UTCEverything below is measured over the latest 5 public posts (spanning ~13415 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0
Top of the latest posts
@adnan360 We are likely to go Epicyon at some point, which is enhanced for #NoScript and #onionRouting and #garlicRouting. #makeJavascriptOptional @Decentralize_today @hyde @FisaCourtHoarder @icedquinn
@icedquinn Woops, yes, we were thinking of clearnet use cases but yes the similar traffic analysis issues apply, simply due to the fact that Tor devs mysteriously discourage the development of #torrenting and #garlicRouting over #Tor, while
@icedquinn Tor has #deanonymising elements inherant to it, as #exitNodes can be setup to limit traffic speeds, which can then be used at the #TorGuard node and/or #ISP to track users. That's just one of the many reasons why #i2p and #garlic
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/garlicrouting