#lockf
Live, measured metrics for the hashtag #lockf from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #lockf
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 22:05 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 22:05 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 22:05 UTCEverything below is measured over the latest 7 public posts (spanning ~12 hours).
Posting hours (UTC)
Languages: English (7)
Avg boosts / post: 0.4
Top of the latest posts
@josephholsten @ska @synlogic @cks @sourcejedi_ben Yes, another one. I've just discovered the existence of Michael Tokarev's lckdo, which is a little odd. It falls back to flock(2) in the absence of fcntl(2) lock calls. I wonder what system
@ska @josephholsten @cks @synlogic @sourcejedi_ben The problem with that is, as I mentioned, no-one cares about the standard when the world has patently gone with #flock(2), there actually _is_ an Linux standard covering flock(2) anyway, an
@ska Of course, those arguments work in the opposite direction, too. - fcntl(2) is objectively the wrong interface, as using _record_ locking of 1 giant record instead of a whole-file lock, when the utility is locking a whole lock _file_, i
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/lockf