#markupsafe
Live, measured metrics for the hashtag #markupsafe from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #markupsafe
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 11:02 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 11:02 UTCNo related tags with measured usage found for #markupsafe.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:02 UTCEverything below is measured over the latest 5 public posts (spanning ~3946 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 6
Top of the latest posts
Python has seen significant performance improvements in the last few releases. MarkupSafe has a C extension to speed up operations, but it's now *slower* in many cases than the plain Python implementation. Having a C extension increases the
MarkupSafe speedup saga continues: my coworker contributed a PR to implement them in Rust now. It uses some pretty clever speedups based on other serialization libraries they surveyed. If anyone is comfortable with Rust, we would appreciate
Update on my "remove MarkupSafe's C speedups" post: @tonybaloney swooped in and found a simple change that make the speedups ~40% faster in the cases where they had become slower. Turns out, if plain strings are the most probable thing you'
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/markupsafe