#oom
Live, measured metrics for the hashtag #oom from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #oom
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 04:53 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 04:53 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 04:53 UTCEverything below is measured over the latest 40 public posts (spanning ~13856 hours).
Posting hours (UTC) — busiest: 01:00
Languages: English (25) · Russian (8) · Dutch (2) · French (2) · Chinese (Taiwan) (1) · Ukrainian (1)
Avg boosts / post: 0.2
Top of the latest posts
Why does the linux kernel not automatically warn somehow when RAM OOM is about to happen? Is that really so hard? Or do the applications just launch and say 'sod it, not my problem, let's go' and the OS says 'Not my job to stop anything' ?
Next one. She's still in need of a name. I like Peaches, but I heard that's a pretty oldtimey name? #orborbmagi #oom #pixelart #魔法少女
Adjust OOM killer scores for critical daemons like sshd or systemd-journald to prevent termination under memory pressure. Write values from -1000 to 1000 to /proc/[pid]/oom_score_adj to lower or raise kill priority. Works on Linux 2.6.36+,
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/oom