#fscheck
Live, measured metrics for the hashtag #fscheck from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fscheck
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 · mastodon.social (Mastodon public tags API) · fetched 2026-09-29 07:27 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-09-29 07:27 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-29 07:27 UTCEverything below is measured over the latest 11 public posts (spanning ~18690 hours).
Posting hours (UTC)
Languages: English (11)
Avg boosts / post: 0.9
Top of the latest posts
This suggestion worked, thanks again: #fsharp #fscheck --- RT @algunion @breki74 Try this approach instead, and only "return" once. #fsharp https://twitter.com/algunion/status/1591761595679772672
learning the library #FsCheck I guess the definition of NonEmptyString is different..
I am slowly getting the hang of this #propertybasedtesting thing ;-) #FSharp #dotnet #FsCheck #xunit
#fscheck across platforms
every network with a public tag surfaceFollow #fscheck straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/fscheck