#notsco
Live, measured metrics for the hashtag #notsco from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #notsco
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-28 08:04 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-28 08:04 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 08:04 UTCEverything below is measured over the latest 6 public posts (spanning ~962 hours).
Posting hours (UTC)
Languages: English (6)
Avg boosts / post: 0.8
Used together with
Top of the latest posts
With permission, someone using #NOTSCO for the first time. Shows how they are working through the process step by step. Exactly what the system is meant to do. It is something #TOTSCO lack in any form.
With permission, someone using #NOTSCO for the first time. Shows how they are working through the process step by step. Exactly what the system is meant to do. It is something #TOTSCO lack in any form.
I’m planning some updates to #NOTSCO today to allow a lot more combinations of match response. Trying to cover off the #TOTSCO examples to make high level testing work better. We can make our match responses simple, they are. But we have to
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/notsco