#lexer
Live, measured metrics for the hashtag #lexer from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #lexer
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:14 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:14 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:14 UTCEverything below is measured over the latest 19 public posts (spanning ~66964 hours).
Posting hours (UTC) — busiest: 01:00
Languages: English (14) · Russian (2) · German (1) · Spanish (1)
Avg boosts / post: 0.4
Top of the latest posts
Beating the Fastest Lexer Generator in Rust, https://alic.dev/blog/fast-lexing. #RustLang #performance #lexer
Damn. My PLY lexer doesn't recognize hexadecimal numbers, it recognizes them as decimal(0) and symbol(x1). edit: oh, it's a matter of definition order. #parser #lexer
https://tratt.net/laurie/blog/2023/why_split_lexing_and_parsing_into_two_separate_phases.html #parser #lexer #ast
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/lexer