#kqueue
Live, measured metrics for the hashtag #kqueue from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #kqueue
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 · mas.to (Mastodon public tags API) · fetched 2026-10-15 06:45 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-10-15 06:45 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-15 06:45 UTCEverything below is measured over the latest 40 public posts (spanning ~17029 hours).
Posting hours (UTC) — busiest: 06:00
Languages: English (37) · German (1)
Avg boosts / post: 0.6
Top of the latest posts
Finally some progress again with #Xmoji (#X11 #emoji #keyboard): Added the history tab! History is persisted in a config file that should also hold other runtime config later and is watched for changes. For now, I only implemented the naive
I use #BSD and hence #kqueue instead of epoll. But I also use #libevent via ffi (from a couple/few different langs) and it abstracts over epoll/kqueue very nicely. https://libevent.org/ #OpenBSD uses it in some of their daemons which gives
👨💻💾 Oh, you need to reinvent the wheel for detecting file changes on macOS? 🙄 Congrats on discovering #kqueue, the tool that's literally older than your dev career! But hey, at least you got a blog post out of it. 🚀🎉 https://www.vega
What “kqueue” means
WikipediaKqueue is a scalable event notification interface introduced in FreeBSD 4.1 in July 2000, also supported in NetBSD, OpenBSD, DragonFly BSD, and macOS. Kqueue was originally authored in 2000 by Jonathan Lemon, then involved with the FreeBSD Core Team. Kqueue makes it possible for software like nginx to solve the c10k problem. The term "kqueue" refers to its function as a "kernel event queue"
“Kqueue” on Wikipedia (CC BY-SA) →#kqueue across platforms
every network with a public tag surfaceFollow #kqueue straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/kqueue