#sysprof
Live, measured metrics for the hashtag #sysprof from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #sysprof
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-27 10:17 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-27 10:17 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 10:17 UTCEverything below is measured over the latest 40 public posts (spanning ~20252 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (40)
Avg boosts / post: 1.9
Top of the latest posts
5 days ago, I encountered a "somewhat serious, but niche" performance bug in #Inkscape where it would lock up the whole application while eating the CPU for 10 minutes when ungrouping thousands of objects at once (hello, EPS-imported files
For a long time I've been intrigued by #Epiphany taking 3 to 20 seconds to load most websites on startup or in Incognito Mode. Today I tested a bunch of configurations to report a bug, profiled… and it turned out to be 2 bugs in 1 :blobswea
I stumbled upon a 2300-pages-long PDF document that actually is a fantastic benchmark for slow search performance (1.5 to 5 minutes) in most PDF readers (including GNOME Papers, Evince and Okular)… so I fired up #Sysprof through GNOME Build
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/sysprof