#cmakepresets
Live, measured metrics for the hashtag #cmakepresets from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #cmakepresets
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-28 08:16 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-28 08:16 UTCNo related tags with measured usage found for #cmakepresets.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 08:16 UTCEverything below is measured over the latest 2 public posts (spanning ~6715 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0.5
Top of the latest posts
wrote my first CMakePresets.json file yesterday. I like it, I guess? Now I don't have to write a Makefile or a BUILDING.md that is just copypasta of my command line arguments. Can just say "use the xyz cmake preset" 1. Why json? (but at lea
In my never-ending quest to master CMake, I developed a few opinions on how I want my projects to work and finally looked at "CMake Presets" in my latest article. #CMake #CmakePresets #CTest #Cpp https://martin-fieber.de/blog/cmake-presets/
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/cmakepresets