#fsync
Live, measured metrics for the hashtag #fsync from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fsync
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-28 07:35 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-28 07:35 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 07:35 UTCEverything below is measured over the latest 20 public posts (spanning ~58294 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (13) · Russian (4) · Chinese (1) · Chinese (Taiwan) (1)
Avg boosts / post: 0.5
Top of the latest posts
I've been studying fsync() for a couple of years and I thought I'd seen every weird way that it could be used and misused, but this week I learned of one more that exists in the wild: if the program crashes between write() and fsync(), on r
So finally got the #ntsync #wine patches applied to #Proton and went to test it on #GuildWars2. In the Omphalos chamber in the Grove, #fsync and #esync yielded about 74fps, both off yielded 84 (odd, I know). After allowing my user to access
The antonomy of #XFS #fsync https://dev.to/yugabyte/the-anatomy-of-xfs-fsync-4ael #fs #linux #filesystem #kernel
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/fsync