#ScratchGPIO
Live, measured metrics for the hashtag #ScratchGPIO from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #scratchgpio
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 07:12 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 07:12 UTCNo related tags with measured usage found for #scratchgpio.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:12 UTCEverything below is measured over the latest 7 public posts (spanning ~10707 hours).
Posting hours (UTC)
Languages: English (7)
Avg boosts / post: 0.7
Top of the latest posts
For my next clock project, I'm thinking of resurrecting my old #ScratchGPIO #TopsyTurvy clock that was inspired by @Workshopshed one https://www.workshopshed.com/2014/09/a-working-topsy-turvy-clock/ But this time programming it using @micro
I have finally started on converting #ScratchGPIO to #Python3 :) Using good old #PiBrella for testing
I'm going to try and make a slight bug fix to my >10 year old #Python2 #ScratchGPIO project - wish me luck!
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/scratchgpio