#callgraph
Live, measured metrics for the hashtag #callgraph from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #callgraph
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-29 17:56 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-29 17:56 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 17:56 UTCEverything below is measured over the latest 4 public posts (spanning ~10292 hours).
Posting hours (UTC)
Languages: English (2) · German (1) · Basque (1)
Avg boosts / post: 0.8
Top of the latest posts
@joxean I think a fine-grained callgraph including call site information would break this tie. Match the call sites in the two binaries, using instruction-level comparisons. You can then differentiate between the two call edges, based on wh
What happens during a #TYPO3 #v13 frontend call? #DDEV integrates the #PHP #Profiler #XHProf which visualizes the process as a #svg #callgraph. This will be useful for research in our #Translation Handling #Initiative. Are you able to follo
I'm happy to share that I just released #MetaCG version 0.5.0 \o/ Besides a number of important bug fixes, we have *finally* reworked some internals that gave us a great performance improvement. For several use cases from minutes to seconds
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/callgraph