#damo
Live, measured metrics for the hashtag #damo from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #damo
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-27 23:54 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-27 23:54 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 23:54 UTCEverything below is measured over the latest 40 public posts (spanning ~21897 hours).
Posting hours (UTC) — busiest: 21:00
Languages: English (39)
Avg boosts / post: 0.7
Top of the latest posts
I just posted the last DAMON quaterly news letter for 2024: https://lore.kernel.org/[email protected] In short, we got more users, features, and presentation/documents. #linux #kernel #damon #damo #quaterly_newsletter #20
Just released damo v2.6.1. Using this version and kernels that built with an RFC patch series, you can try page level properties based access monitoring. For example, you can know how much of anonymous and non-Young pages are in regions of
DAMON user-space tool v3.0.9 and later supports recording data access pattern on Android. Kudos to @rostedt since this change was inspired from a chat that I had with him at LPC'25. [1] https://damonitor.github.io/posts/damo_support_trace_c
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/damo