#nlohmann
Live, measured metrics for the hashtag #nlohmann from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #nlohmann
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.online (Mastodon public tags API) · fetched 2026-07-28 06:25 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-07-28 06:25 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-28 06:25 UTCEverything below is measured over the latest 4 public posts (spanning ~16613 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 0.3
Top of the latest posts
I've made a fix PR for #nlohmann json https://github.com/nlohmann/json/pull/4654
Interesting. The C++ JSON parser by Niels Lohmann that is a more or less defacto standard seems to parse things wrong, or at least give out wrong value when getting named values from a nlohmann::json instance. Very weird, as it used to work
First time I'm properly using the nlohmann JSON parser for C++. it works using rocket magic and at least I have no idea what the code actually does by looking at it. :) But when you do something wrong you're in for hellish templated error m
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/nlohmann