#tridge
Live, measured metrics for the hashtag #tridge from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tridge
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.online (Mastodon public tags API) · fetched 2026-09-25 18:18 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.online (Mastodon public search API) · fetched 2026-09-25 18:18 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-25 18:18 UTCEverything below is measured over the latest 8 public posts (spanning ~14991 hours).
Posting hours (UTC)
Languages: English (8)
Avg boosts / post: 1.5
Top of the latest posts
Here's the question we're all wondering about that I haven't seen asked yet... #rsync #slop #tridge #sailing
https://alexispurslane.github.io/rsync-analysis/ #rsync #tridge #llm
Regarding all the noise about rsync, here is a pretty nuanced take by the Perpetrator of All Evil himself: https://medium.com/@tridge60/rsync-and-outrage-d9849599e5a0 I've used tridge's stuff (samba and rsync) professionally for 25 years, p
#tridge across platforms
every network with a public tag surfaceFollow #tridge 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/tridge