#formalverification
Live, measured metrics for the hashtag #formalverification from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #formalverification
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-10-17 07:08 UTC1 uses by 1 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-10-17 07:08 UTCNo related tags with measured usage found for #formalverification.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-10-17 07:08 UTCEverything below is measured over the latest 40 public posts (spanning ~2502 hours).
Posting hours (UTC) — busiest: 01:00
Languages: English (38) · German (1)
Avg boosts / post: 0.8
Top of the latest posts
Announcing the July FPIndia #Bangalore #Meetup lineup! 1. Ramit will talk about Symbolic Trajectory Evaluation to verify ECC #FormalVerification 2. Anupam will talk about Type Generic Programming techniques in #Haskell Also now you can RSVP
My new Lean formalization, from a quantum many-body reading point: the W-state locality obstruction / Corollary 1 of Gioia–Moudgalya–Motrunich. Formalizing it surfaced a useful refinement: equal duplicate-free creator supports specify the s
@adolfont.github.io Muito bom. *Papers With Lean* gives us a curated reading point. `#LeanLang` here and `#LeanProver` at another location give us other reading points. Each usage gives us specificity: \[ \text{location} \longrightarrow \te
#formalverification across platforms
every network with a public tag surfaceFollow #formalverification 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/formalverification