#mitmproxy
Live, measured metrics for the hashtag #mitmproxy from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #mitmproxy
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 · mastodon.online (Mastodon public tags API) · fetched 2026-10-20 12:37 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-10-20 12:37 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-20 12:37 UTCEverything below is measured over the latest 40 public posts (spanning ~11983 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (34) · Russian (4) · Czech (1) · German (1)
Avg boosts / post: 0.2
Top of the latest posts
I’ve started doing something simple when local LLM behavior feels “off”: I inspect the wire. In this piece, I show how I route Quarkus → Ollama traffic through mitmproxy to see the real `/v1/chat/completions` payload, compare plain vs tool-
I am working with some #embedded #esp32 #websocket for #ClassQuiz. It took me hours why the websocket connection would seemingly random collapse. Now I figured it out after debugging for hours: I configured a timeout for the network socket
Debug HTTP/HTTPS traffic with a 180-line Python proxy script for mitmproxy. Intermediate level. Logs requests, headers, and bodies for web apps, microservices, and mobile clients. Runs https://www.valtersit.com/python/http-request-inspector
#mitmproxy across platforms
every network with a public tag surfaceFollow #mitmproxy straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/mitmproxy