#keyboardinterrupt
Live, measured metrics for the hashtag #keyboardinterrupt from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #keyboardinterrupt
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 03:11 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 03:11 UTCNo related tags with measured usage found for #keyboardinterrupt.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 03:11 UTCEverything below is measured over the latest 2 public posts (spanning ~0.5 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0.5
Used together with
Top of the latest posts
... So now have near the top before any other imports ... import signal def _end_it(*_): raise SystemExit( 'Program aborted.' ) signal.signal( signal.SIGINT, _end_it ) signal.signal( signal.SIGTERM, _end_it ) #Python #KeyboardInterrupt
Is catching "#KeyboardInterrupt" in a "try-except" (visibly rather long at ~24 lines) block any better|worse than using signal? /--- Ah, one advantage of using signal would be to cover imports too (besides the import of "signal"+set up), wh
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/keyboardinterrupt