#win32k
Live, measured metrics for the hashtag #win32k from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #win32k
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 05:26 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 05:26 UTCNo related tags with measured usage found for #win32k.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 05:26 UTCEverything below is measured over the latest 8 public posts (spanning ~28571 hours).
Posting hours (UTC)
Languages: English (7) · Italian (1)
Avg boosts / post: 0.1
Top of the latest posts
Both win32kbase_rs.sys and win32kfull_rs.sys from Windows 11 Insider Preview 25357.1 are indexed for download now on Winbindex as well! https://winbindex.m417z.com/?arch=insider&file=win32kbase_rs.sys https://winbindex.m417z.com/?arch=insid
Starting to reverse the actual Win32k GDI Rust structures inside win32kbase_rs now too... Mostly trying to figure out REGION_CORE and friends. I think this rgncore::RegionCore::intersects function was a simple place to start and looks OK so
Another win32k Rust diagram here, showing how calling the C function NtGdiPtInRegion (exported from win32kbase) ends up calling in to the Rust function rgncore::RegionCore::contains_point (inside win32kbase_rs) ! There's a "shim" function n
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/win32k