#httpserver
Live, measured metrics for the hashtag #httpserver from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #httpserver
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 23:47 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 23:47 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 23:47 UTCEverything below is measured over the latest 19 public posts (spanning ~59964 hours).
Posting hours (UTC) — busiest: 22:00
Languages: English (13) · Spanish (2) · German (1) · Chinese (Taiwan) (1)
Avg boosts / post: 0.2
Top of the latest posts
One Open-source Project Daily Ngrok FRP Alternative • Fast • Lightweight • 0 Dependency • Pluggable • TLS interception • DNS-over-HTTPS • Poor Man's VPN • Reverse & Forward • "Proxy Server" framework • "Web Server" framework • "PubSub" fram
Vuln Management InfoSec folks, given the state of web servers, what are we running production and feeling least hesitation about? I’m weary of Apache and NGINX at the moment, but wonder what others are thinking. Which do you trust exposed t
#Apache :apache: #HTTPServer: Hochriskante Lücken ermöglichen Einschleusen von Schadcode | Security https://www.heise.de/news/Apache-HTTP-Server-Hochriskante-Luecken-ermoeglichen-Einschleusen-von-Schadcode-11284090.html #Patchday
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/httpserver