#pythonLapidary
Live, measured metrics for the hashtag #pythonLapidary from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pythonlapidary
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 · mas.to (Mastodon public tags API) · fetched 2026-07-27 07:45 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-27 07:45 UTCNo related tags with measured usage found for #pythonlapidary.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 07:45 UTCEverything below is measured over the latest 3 public posts (spanning ~9079 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 2
Top of the latest posts
Lapidary-render 0.12.0 is now released. To the best of my knowledge it's the only #codeGenerator that properly handles #jsonSchema anyOf and allOf. Also has support for oneOf, but not per the specs. https://github.com/python-lapidary/lapida
Does it still make sense to maintain deterministic code generators? I mean for #OpenAPI. Since #JSONSchema translates so badly to classes in any programming language, generating with #LLM might work better with guessing what the author of t
I wanted to build a #python client for some #openSource project that offers a good #openApi 3.0 description - just to test my generator on real-live service, but also to support the community. I looked at @forgejo but it turns out it uses s
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/pythonlapidary