#liquidhaskell
Live, measured metrics for the hashtag #liquidhaskell from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #liquidhaskell
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 23:24 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 23:24 UTCNo related tags with measured usage found for #liquidhaskell.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 23:24 UTCEverything below is measured over the latest 40 public posts (spanning ~25177 hours).
Posting hours (UTC) — busiest: 04:00
Languages: English (40)
Avg boosts / post: 1.3
Top of the latest posts
tutorial on #liquidhaskell abstract refinements that I wrote a couple years ago and never published before now: https://curious.software/static/absref-draft.html
I am yet again starting a project in #haskell and having fun getting lost in something fun, but basically causing me to be side-tracked. I'm working on a simple pixel art editor, but I am excited by #LiquidHaskell to, I think, use refinemen
Feeling great about my recent post @tweag's software engineering blog! It tells the story of how (and why) I implemented qualified identifier support for refinement type aliases in #LiquidHaskell during my participation at #GSoC 2025. Check
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/liquidhaskell