#libconfig
Live, measured metrics for the hashtag #libconfig from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #libconfig
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-09-29 02:03 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-09-29 02:03 UTCNo related tags with measured usage found for #libconfig.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-09-29 02:03 UTCEverything below is measured over the latest 2 public posts (spanning ~6907 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Used together with
Top of the latest posts
Today's bug is minor `libconfig` test suite failure: https://github.com/hyperrealm/libconfig/pull/260 There on 32-bit systems (and only on 32-bit ones) the config pretty-printer started prepending 32 leading zeros to binary integers: bin_in
Super-glad I ditched the #libconfig dependency in the C++ project I was using it in. All the vcpkg maintainers have done since I reported the issue is put a tag on the report.
#libconfig across platforms
every network with a public tag surfaceFollow #libconfig 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/libconfig