#utmps
Live, measured metrics for the hashtag #utmps from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #utmps
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 12:10 UTC1 uses by 1 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 12:10 UTCNo related tags with measured usage found for #utmps.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:10 UTCEverything below is measured over the latest 9 public posts (spanning ~10407 hours).
Posting hours (UTC)
Languages: English (9)
Avg boosts / post: 0
Top of the latest posts
@ska It's interesting how close but still how frustratingly far off #FreeBSD is in this regard. The setlogin() name is per-session, not per-process. But whilst there is a sysctl() for snapshotting the process list, there isn't one for snaps
@cks The sad thing is, as I was saying last year, all of this is unnecessary. The kernels, #FreeBSD, #NetBSD, #OpenBSD, and #Linux, all maintain almost all of the stuff that 'who' needs, and have done since the switch to POSIX sessions and
@ska #s6 doesn't even have anything dealing generally with the #Unix accounts database in the first place, does it? That is more the domain of nsss and utmps, ne? #utmps #nsss
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/utmps