#openapiprocessor
Live, measured metrics for the hashtag #openapiprocessor from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #openapiprocessor
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-29 22: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 · fosstodon.org (Mastodon public search API) · fetched 2026-07-29 22:27 UTCNo related tags with measured usage found for #openapiprocessor.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 22:27 UTCEverything below is measured over the latest 32 public posts (spanning ~29245 hours).
Posting hours (UTC) — busiest: 07:00
Languages: English (32)
Avg boosts / post: 0.8
Used together with
Top of the latest posts
now, before a release, I have the boring task to extend all the integration tests with a record version. 😉 #openapiprocessor #openapi #springframework 2/2
released openapi-processor-spring/micronaut 2023.1.2 it fixes additional parameters in combination with bean validations. See the core release notes [2023.1.2](https://github.com/openapi-processor/openapi-processor-base/releases/tag/v2023.1
released openapi-processor-spring/micronaut 2026.3 it fixes a few issues and it is now possible to generate (Spring) `@HttpExchange` annotations and use the generated interfaces for server or client side implementation. For Micronaut this i
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/openapiprocessor