#industrialmanslaughter
Live, measured metrics for the hashtag #industrialmanslaughter from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #industrialmanslaughter
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-08-02 17:29 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-08-02 17:29 UTCNo related tags with measured usage found for #industrialmanslaughter.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-02 17:29 UTCEverything below is measured over the latest 7 public posts (spanning ~25761 hours).
Posting hours (UTC)
Languages: English (7)
Avg boosts / post: 0.1
Top of the latest posts
@jmcrookston The content of the article has Musk's company with an unsecured & unstable beam 50 feet up and a worker immediately adjacent to that beam not knowing the beam was unstable and not secure. We've got "industrial manslaughter" in
@sdhamiltonvic.bsky.social " adopting the four Cs of curiosity, contestability, collaboration and courage — as a sound decision-making framework. “[This approach] will always ensure the robust and innovative thinking necessary in this impor
4/? The currently-in-place alternative, to having #IndustrialManslaughter apply in situations like #RoboDebt, is letting bureaucratic mismanagement, political grandstanding, victimisation of the already marginalised, lies, cowardice and bul
#industrialmanslaughter across platforms
every network with a public tag surfaceFollow #industrialmanslaughter straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/industrialmanslaughter