#minicoredumper
Live, measured metrics for the hashtag #minicoredumper from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #minicoredumper
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-10-03 21:18 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-10-03 21:18 UTCNo related tags with measured usage found for #minicoredumper.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-03 21:18 UTCEverything below is measured over the latest 2 public posts (spanning ~7359 hours).
Posting hours (UTC)
Languages: English (1) · German (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
TIL: thread stacks will not be marked in /proc/<pid>/task/<tid>/maps correctly, instead the kernel reports the mapping of the main thread for all threads of a process. If you actually want to know a threads stack, you have to obtain it's St
Also, as a word of caution: if you use the #minicoredumper to create compact corefiles, it will refuse to dump such an application, due to the size of the elf-headers of the created core-elf.
#minicoredumper across platforms
every network with a public tag surfaceFollow #minicoredumper 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/minicoredumper