#ecma35
Live, measured metrics for the hashtag #ecma35 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ecma35
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 09: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-27 09:04 UTCNo related tags with measured usage found for #ecma35.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:04 UTCEverything below is measured over the latest 4 public posts (spanning ~17041 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 0
Used together with
Top of the latest posts
@stafwag All in all, getting it right, and compatible with what's out in the world, is quite a task. Many of us end up with entire DEC VT state machines. Because it turns out that it's perfectly legitimate to emit some C0 control characters
@stafwag And then once control sequences are parsed correctly, on top of that there are four different types of control sequence used in the wild for setting colours: old AIXterm, XTerm 256-colour, ITU/IEC T.416 faulty, and ITU/IEC T.416 co
@stafwag Colours in ncurses. Ouch! Your SGR parser is a bit simplistic. The basic syntax of control sequences in ECMA-35 and ECMA-48 is a bit more complex than that. More than digits can be parameter characters, and there are intermediate 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/ecma35