#OOPSLA22
Live, measured metrics for the hashtag #OOPSLA22 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #oopsla22
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 13:33 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 13:33 UTCNo related tags with measured usage found for #oopsla22.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 13:33 UTCEverything below is measured over the latest 3 public posts (spanning ~0 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 1.3
Used together with
Top of the latest posts
#OOPSLA22 Saturday morning: @casvdrest on defining and composing safe-by-construction programming language components in Agda. Assemble safe-by-construction languages from reusable, concise, safe-by-construction components! Paper: https://d
#OOPSLA22 Saturday morning: @virtlink on automatically deriving IDEs with static semantic completion from declarative typing rules. Only static semantically valid code completion suggestions, based on the static semantics of your language!
First day of #SPLASH22 in Auckland NZ! Looking forward to an interesting program today and the days ahead. Shameless plug: if you're attending, you should consider attending the #OOPSLA22 talks linked below.
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/oopsla22