#iwm
Live, measured metrics for the hashtag #iwm from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #iwm
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 16:47 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 16:47 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 16:47 UTCEverything below is measured over the latest 40 public posts (spanning ~16648 hours).
Posting hours (UTC) — busiest: 02:00
Languages: English (30) · German (9)
Avg boosts / post: 0.5
Top of the latest posts
I just ran some comparisons of the iwm(4) and the iwlwifi(4) drivers for my FreeBSD 15.1-RELEASE Lenovo X1 Carbon (gen 6). After three tests of each driver the results suggest that: 1) iwlwifi is a more reliable connection (across jitter, l
So, after I met problems with iwlwifi driver and my attempts to aggregate both em0 and wlan0 interfaces to the one lagg0 interface (https://mastodon.bsd.cafe/@evgandr/115985853500057386) — looks like I found a much (MUCH!) simpler solution
Think it is time to give the #iwlwifi driver a try on #FreeBSD 15.0 for my Intel 8260 wireless card. So far so good, might get some speed gain compared with #iwm driver but I need to run a few days to make a conclusion. Wiki page here is he
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/iwm