#Devdrive
Live, measured metrics for the hashtag #Devdrive from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #devdrive
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 02:36 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 02:36 UTCNo related tags with measured usage found for #devdrive.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 02:36 UTCEverything below is measured over the latest 16 public posts (spanning ~18090 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (16)
Avg boosts / post: 1.1
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
Blogged: Test-Driving #Windows 11 Dev Drive for .NET 🔍 What is #DevDrive and ReFS? 🧪 Trying it out for various scenarios ➡️ #dotnet, #jvm, @JetBrainsRider, and more https://bit.ly/3GcOPhU
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):
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/devdrive