#WireGuardVPN
Live, measured metrics for the hashtag #WireGuardVPN from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #wireguardvpn
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 04:24 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 04:24 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 04:24 UTCEverything below is measured over the latest 33 public posts (spanning ~49621 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (23) · German (8) · Russian (2)
Avg boosts / post: 0.9
Top of the latest posts
@davidgerard I use @beasts and #ovh. I do a bit of web, some #WireGuardVPN and email on both systems and manage it all myself. Both are fine and cheapish. I used to use #bytemark but they got swallowed up by iomart.
I just finished writing a tutorial for setting up Nextcloud AIO behind a Wireguard VPN. ( all local setup) go check it out if want a guide to get started with this setup https://help.nextcloud.com/t/nextcloud-aio-tutorial-with-caddy-reverse
I wrote up how I got #vxlan working over #wireguard #WireGuardVPN on #openbsd as with most things on OpenBSD not that complicated 🙌🏼 https://rob-turner.net/post/vx-lan/
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/wireguardvpn