#refs
Live, measured metrics for the hashtag #refs from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #refs
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 23:48 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 23:48 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 23:48 UTCEverything below is measured over the latest 40 public posts (spanning ~30330 hours).
Posting hours (UTC) — busiest: 20:00
Languages: English (32) · Russian (3) · German (3) · Spanish (1) · Portuguese (1)
Avg boosts / post: 0.3
Top of the latest posts
I'm seeing an observable behavior difference in File.Replace() between Win10 NTFS and Win11 ReFS (DevDrive): https://github.com/KirillOsenkov/Misc/blob/adbd3df4a30d378f0c3c1e4c8e87d2f41501ae2a/FileReplace.cs#L6-L20 On regular C: drive I get
First time poking around with Dev Drives, so doing a little performance testing by measuring `dotnet build` after `git clean -xdf` for @xunit (`main` branch). On NVMe (NTFS): 17.5s On SATA (NTFS): 17.9s On VHDX (ReFS): 14.4s On VHDX (ext4):
Rapid Refresh Forecast System (RRFS) - Rapid Refresh Forecast System (RRFS) - Philadelphia Weekend Weather & Storm Forecasts — #RRFS #REFS #RRFS-A Posted Thursday 07/16/26 @ 5:05 PM — It’s come to my attention that a public web page on GitH
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/refs