#kernelmodules
Live, measured metrics for the hashtag #kernelmodules from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #kernelmodules
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 07:59 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 07:59 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:59 UTCEverything below is measured over the latest 6 public posts (spanning ~14933 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 3.2
Top of the latest posts
And here I am sitting in front of four working monitors (three external, two via #HDMI, one via #USBC), all configured through #KDE and using #Displaylink and #EVDI #KernelModules without any faffing around, except for plugging things into
@mboelen This is regarding your wonderful article https://linux-audit.com/kernel/kernel-hardening-disable-and-blacklist-linux-modules/. It is stated in this article there is also an alias option. This might be used to redirect a module to /
Modernised use of freebsd-update for minor and major upgrades to FreeBSD A major upgrade example: 14.4-RELEASE to 15.1-RELEASE All commands should be run as root. pkg update pkg upgrade -Uy -r FreeBSD pkg freebsd-update fetch freebsd-update
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/kernelmodules