#dnshaiku
Live, measured metrics for the hashtag #dnshaiku from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dnshaiku
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 20:50 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 20:50 UTCNo related tags with measured usage found for #dnshaiku.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 20:50 UTCEverything below is measured over the latest 4 public posts (spanning ~23827 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 0
Top of the latest posts
Tonight’s home lab project: get a custom subdomain working with Kubernetes so I can access containers at [project].k8s.home. I actually had this working last year, but with newer versions of Kubernetes and new DNS servers in the form of Cor
The home network's DNS seems to be a whole lot better now? I went from several upstream DNS-over-HTTPS servers down to 2 and it seems better. Certainly less failures. That being said, that's the same thing that happened yesterday - it worke
#dnshaiku apple edition? Was working on contacting support for something and DNS wasn't resolving for a particular domain.
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/dnshaiku