#roocode
Live, measured metrics for the hashtag #roocode from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #roocode
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-07-27 05:35 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-07-27 05:35 UTCNo related tags with measured usage found for #roocode.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 05:35 UTCEverything below is measured over the latest 21 public posts (spanning ~9404 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (11) · Russian (5) · Japanese (2) · German (2) · Italian (1)
Avg boosts / post: 0.4
Top of the latest posts
@bagder would be way more into #copilot if #microsoft didn't work for #ice. thus, been exploring #foss alternatives: #roocode #ollama #continue #vscodium
🚨 CVE-2025-65946 (HIGH, CVSS 8.1): Roo-Code (<3.26.7) suffers from a command injection flaw (CWE-77). No auth/user input needed; remote code execution is possible. Patch to 3.26.7+ ASAP! Details: https://radar.offseq.com/threat/cve-2025-65
I even had a few hundred dollars in it. I thought at least I could use it with Roo Code via an OpenAI-compatible API gateway, but that's still way behind... I downgraded back to v5 while swearing at it. I guess I need to migrate more toward
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/roocode