#mod_wsgi
Live, measured metrics for the hashtag #mod_wsgi from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #mod_wsgi
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 · mas.to (Mastodon public tags API) · fetched 2026-07-27 12:30 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-27 12:30 UTCNo related tags with measured usage found for #mod_wsgi.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 12:30 UTCEverything below is measured over the latest 3 public posts (spanning ~9717 hours).
Posting hours (UTC)
Languages: Spanish (1) · French (1)
Avg boosts / post: 0.3
Used together with
Top of the latest posts
Problema actualizando mis servicios WSGI a Python 3.13 https://blog.jcea.es/posts/20241012-mod_wsgi_python3_13.html #Python #WSGI #mod_wsgi
I feel like I'm so close to the finish line, by not using mod-wsgi that was packaged by the distro, in this case Alpine, and instead use #mod_wsgi from #pip. I don't get the segfault core dumped error anymore, which is a huge relief cos tha
« Do not try and use a Python virtual environment from one Python installation or version with mod_wsgi, when mod_wsgi was compiled for a different one. » https://modwsgi.readthedocs.io/en/develop/user-guides/virtual-environments.html#virtu
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/mod_wsgi