#parser
Live, measured metrics for the hashtag #parser from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #parser
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 07:59 UTC1 uses by 1 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 07:59 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:59 UTCEverything below is measured over the latest 40 public posts (spanning ~5202 hours).
Posting hours (UTC) — busiest: 05:00
Languages: English (32) · Russian (5) · Polish (2)
Avg boosts / post: 0.5
Top of the latest posts
It was a cold and rainy day today so I decided to rework the parser of my text adventure game skeleton. So now you can enter a simple sentence as can be seen in the screenshot which is better than the two-word approach I initially implement
New update for my #python #multipart #parser #benchmark: https://defnull.de/2026/python-multipart-benchmark/ The benchmark tests and compares the most commonly used Python parsers for multipart/form-data (HTML5 forms) in different scenarios
Rust rewrite of wikiextractor, processes enwiki dump with template expansion in 24 min (instead of 13h with Python). Output is binary compatible (not counting Python mangling). CLI parameters are identical. New option to output a specific 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/parser