#duperemove
Live, measured metrics for the hashtag #duperemove from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #duperemove
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-10-01 11:14 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-10-01 11:14 UTCNo related tags with measured usage found for #duperemove.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-01 11:14 UTCEverything below is measured over the latest 13 public posts (spanning ~23295 hours).
Posting hours (UTC) — busiest: 21:00
Languages: English (12) · French (1)
Avg boosts / post: 0.3
Used together with
Top of the latest posts
@youam read about that briefly, sounds very nice, the daemon mode sounded very interesting to me to kind of get an inband deduplication like experience / compromise. The reason why I didn't try it yet though was because I couldn't find it i
Also, the #duperemove hash file, an sqlite 3 database it seems, takes up about 10 GiB for this #btrfs partition for me. So that needs to be added to the reported 127G disk usage / 256GiB disk, I guess.
@dbat the same issue exists in the research data management world with #DataLad / #gitAnnex. One thing that I am doing for our storage servers is regularly run #duperemove on it. It requires filesystem support (xfs/btrfs), but deduplicates
#duperemove across platforms
every network with a public tag surfaceFollow #duperemove 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/duperemove