#sniproxy
Live, measured metrics for the hashtag #sniproxy from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #sniproxy
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-29 12:53 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-29 12:53 UTCNo related tags with measured usage found for #sniproxy.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 12:53 UTCEverything below is measured over the latest 5 public posts (spanning ~26813 hours).
Posting hours (UTC)
Languages: English (3) · German (2)
Avg boosts / post: 0.4
Top of the latest posts
What to use to forward SSL connections? #sniproxy tells it's EOLed but is there something else? Or does one need to terminate the SSL connections now?
This afternoon, I got close to what I wanted to achieve in terms of load-balancing between the two #AI #sabots I have running. I had originally planned to use #OpenBSD's #OpenHTTPD or #RelayD to do the job, but #HAProxy #PROXY protocol was
As of 2023-12-13 #sniproxy is marked as deprecated. That's a shame, because there is no equivalent replacement. All other reverse proxies (Nginx, HAProxy, Caddy etc.) are significantly more complex, more resource-hungry or less performant.
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/sniproxy