#wavedashing
Live, measured metrics for the hashtag #wavedashing from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #wavedashing
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-09-26 18:56 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-09-26 18:56 UTCNo related tags with measured usage found for #wavedashing.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-26 18:56 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
#Thunar from #xfce on my #debian testing install showing off its sick #wavedashing moves while yt-dlp downloads a video in the background. Presumably because yt-dlp is creating and destroying files rapidly. #ytdlp #bugs #wavedash
What “wavedashing” means
WikipediaIn video games, an exploit is the use of a feature that gives a substantial unfair advantage to players using it. An exploit can either be an intended game mechanic being abused, or an unintended side effect from a bug or glitch being performed. However, whether particular acts constitute an exploit can be controversial, typically involving the argument that the issues are part of the game, and no changes or external programs are needed to take advantage of them.
“Video game exploit” on Wikipedia (CC BY-SA) →#wavedashing across platforms
every network with a public tag surfaceFollow #wavedashing 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/wavedashing