#pyqtgraph
Live, measured metrics for the hashtag #pyqtgraph from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pyqtgraph
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-07-27 22:00 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-07-27 22:00 UTCNo related tags with measured usage found for #pyqtgraph.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 22:00 UTCEverything below is measured over the latest 40 public posts (spanning ~18862 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (40)
Avg boosts / post: 0.7
Top of the latest posts
@pathunstrom @glyph 💯💯💯 For this reason I added a “used by” section to the #PyQtGraph readme, and when I am contacted outside of GitHub by a user, I encourage them to make a PR adding their project(s) to that section.
@melissawm @jni @simon_brooke @hynek @napari I build them for #PyQtGraph. You use the html builder with a little bit of (emphasis on little) custom css and the sphinx pydata theme looks amazing as a docset. I also disabled sidebars which ma
@veronica Haven't ran into this with QTextCursor (don't use that one in #PyQtGraph) but I ran into some very odd memory cleanup issues with QMenu a while back. https://github.com/pyqtgraph/pyqtgraph/issues/2497#issuecomment-1296137829 Since
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/pyqtgraph