#oop
Live, measured metrics for the hashtag #oop from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #oop
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-11-01 03:11 UTC3 uses by 3 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-11-01 03:11 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-11-01 03:11 UTCEverything below is measured over the latest 40 public posts (spanning ~1031 hours).
Posting hours (UTC) — busiest: 02:00
Languages: English (39) · German (1)
Avg boosts / post: 1.1
Top of the latest posts
This 1987 paper described an intelligent tutoring system for training USAF space operations personnel to estimate a satellite’s orbital elements by looking at a graphic display of its ground track. It was written in Interlisp and LOOPS, the
@molko is: - Writing an ECS (ugh), - Global Entity ID counter increments under A LOCK (WHAT?!). "I might create new entities on a new thread." ...*WHAT?* IT DOESN'T EVEN RETURN MULTIPLE IDs LIKE `glGenBuffers()`. It locks and outputs an ent
@MaddieM4 I also don't like #OOP and I agree that, it is very bad to deal with projects that use OOP and therefore hide complexity and state within closed abstractions, robbing the programmer of transparency and full control over the data h
#oop across platforms
every network with a public tag surfaceFollow #oop 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/oop