#computerssuck
Live, measured metrics for the hashtag #computerssuck from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #computerssuck
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-28 01:55 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-28 01:55 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 01:55 UTCEverything below is measured over the latest 19 public posts (spanning ~24841 hours).
Posting hours (UTC) — busiest: 05:00
Languages: English (19)
Avg boosts / post: 0.3
Top of the latest posts
I can follow up on the `typeset -U` item. If you use `typeset -U` on an array tied to an environment variable, you will make a local copy of the array, which will be empty. It will then remove all the items from the env variable. So zsh int
I didn't mention venvs or nix-shell. I have to figure out PATH for subshells in those two environments. I don't know exactly how that will work yet. Anyway, I have ranted. Thank you and good night. #ComputersSuck
Here's a thing. Does this do what you expect? (I kind of did expect it, because I spent the whole day today reading the relevant sections of the zsh reference.) #ComputersSuck
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/computerssuck