#regexes
Live, measured metrics for the hashtag #regexes from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #regexes
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 08:51 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 08:51 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:51 UTCEverything below is measured over the latest 27 public posts (spanning ~52240 hours).
Posting hours (UTC) — busiest: 00:00
Languages: English (26)
Avg boosts / post: 0.9
Top of the latest posts
@manwar The last one in your examples is wrong, it ends at (2,2), so the answer is false... Anyway, after the nice cup of coffee in my Monday morning, I got to the following #RakuLang #OneLiners -- the first making good use of Raku's nice #
Raku: The match of a regex is automatically stored in $/, and this variable then also provides access to the text before ($/.prematch), to the text after ($/.postmatch), and to the match's position ($/.from and $/.to). Nice. https://docs.ra
@regehr @commodore @dev There is even a (low-severity, a/k/a “cruel”) #PerlCritic policy to discourage everything but $_, @_, $], and numbered #RegularExpression capture variables: https://metacpan.org/pod/Perl::Critic::Policy::Variables::P
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/regexes