#bunkerweb
Live, measured metrics for the hashtag #bunkerweb from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #bunkerweb
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-28 10:58 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-28 10:58 UTCNo related tags with measured usage found for #bunkerweb.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 10:58 UTCEverything below is measured over the latest 8 public posts (spanning ~14731 hours).
Posting hours (UTC)
Languages: German (4) · English (3)
Avg boosts / post: 0.3
Top of the latest posts
#BunkerWeb wiederum ist echt picky bei der Aktivierung des Proxy Protokoll, wenn man die UI eigentlich nur intern will. Und die Aktivierung von #LetsEncrypt mit Anbindung an meinen #PowerDNS Server ist auch absolut schlecht dokumentiert und
Meine #ownCloud oCIS Instanz zum laufen zu kriegen ist aufwändiger als gedacht. Das Teil ist ziemlich pingelig bei CORS, lässt einen damit aber allein im Regen stehen. Mein bisheriges Reverse Proxy Setup mit HAproxy auf der OPNsense ist daf
I finally gave up on #BunkerWeb. Having a WAF and hardened security headers turned out to cause more issues than it was worth. I ended up migrating to #Caddy with caddy-docker-proxy, it gets the job done without any faff. #SelfHosting
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/bunkerweb