#killswitches
Day-by-day usage
measured · mastodon.social (Mastodon public tags API) · fetched 2026-07-24 14:39 UTC0 uses by 0 unique accounts across the window — real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-07-24 14:39 UTCNo related tags with measured usage found for #killswitches.
Live pulse on Bluesky
measured · api.bsky.app (Bluesky public search API) · fetched 2026-07-24 14:39 UTCEverything below is measured over the latest 7 public posts (spanning ~8401 hours).
Posting hours (UTC)
Languages: English (5)
Avg reposts / post: 0.3
Top of the latest posts
“We don’t need to be invaded by the #U.S. to be constrained by the #administration. We could get logged out, geo-blocked, or told a service we rely on is no longer available under revised terms.” #Canada #KillSwitches
@[email protected] Danke, den Artikel finde ich sehr wichtig. Ein Grund mehr, für Verantwortliche in der Wirtschaft usw... auf Linux umzustellen und dort die von US-Konzernen unabhängige Entwicklung finanziell zu fördern. #Divers
Dorothea Zwölfer (sie)@d-zwoelfer.federation.network.ap.brid.gy♥ 1↻ 02025-12-26 11:08 UTCView on Bluesky →"NOPE!" NVIDIA say no to adding backdoors and killswitches in their GPUs buff.ly/Z11321I #Nvidia #Backdoors #Killswitches #GPU #Hardware #Security #Vulnerability #Tech
Every number above is measured from a named public API at the shown fetch time — nothing estimated, nothing extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON — /api/hashtags/killswitches