The GitHub page for the RAM-Altman task consists of a dry-run choice that any Linux user with a Bash terminal ought to have the ability to paste and run without the requirement for e-mail trolling. When the limit is gone beyond, each dry run output functions one produced joke e-mail, so repetitive runs produce various entertaining examples.

git clone https://github.com/IainKay/ram-altman.git
cd ram-altman
chmod +x ram-altman.sh test-ram-altman.sh

./ram-altman.sh --status    # see the evidence against you
./ram-altman.sh --dry-run   # preview an email without sending it

A trial run of the script on my Fedora 44 KDE device verified the author’s measurements. Inside the System– Info Center of my Fedora desktop, the system reports 14.9 GiB of overall functional system RAM after the kernel and firmware take their required pieces of the 16 GiB of physical memory. This shows the overall quantity of capability the system needs to deal with, not the quantity offered at any offered time. The Ram-Altman script reveals that of that 14.9 GiB overall swimming pool, 10 GiB is utilized, with 4.9 GiB offered (33.1 percent). That figure isn’t the basic amount of the “complimentary” and “cache” lines that the script display screens, however a kernel-calculated figure that represents the total of memory that can be recovered.

nick@fedora:~$ git clone https://github.com/IainKay/ram-altman.git
cd ram-altman
bash ram-altman.sh --dry-run
Cloning into 'ram-altman'...
remote: Enumerating objects: 9, done.
remote: Counting objects: 100% (9/9), done.
remote: Compressing objects: 100% (9/9), done.
remote: Total 9 (delta 2), reused 3 (delta 0), pack-reused 0 (from 0)
Receiving objects: 100% (9/9), done.
Resolving deltas: 100% (2/2), done.
Total:      14.9 GiB
Used:       10.0 GiB
Available:  4.9 GiB (33.1%)
  Free:     1.8 GiB
  Cache:    2.4 GiB

From: sender-not-set@example.com
To: recipient-not-set@example.com
Subject: Unused RAM detected in the wild
Date: Mon, 09 Nov 2026 10:10:43 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated

Hi Sam,

Daily status report:

  Total RAM:     14.9 GiB
  Available:     4.9 GiB (33.1%)
  Threat level:  someone at OpenAI might notice

Stay allocated,
A concerned RAM owner

--
Sent automatically, at most once a day, by a small script on one PC.
Reply if you'd like it to stop.

The task yields the subtlety that Altman was describing just how much time memory invests being used, while the script determines just how much capability is totally free at the time of measurement. While the script may inform Altman that 33 percent of your system RAM is offered, it does not describe how typically that’s the case. The concession actions on the joke a little, however it keeps everybody truthful.

The GitHub is a good idea to explain that”--dry-run is the very best method to enjoy this. It costs absolutely nothing and all the jokes exist.” Utilized irresponsibly, this saucy joke might change into a harassment tool, and Kay rapidly explains that the script does not consist of anybody’s e-mail, consisting of Altman’s. Users who release their own operating variation are motivated to just utilize their own genuine e-mail addresses and honor any demands to stop, as is laid out at the bottom of the script-generated output.

If you’re interested in having a look at a few of the e-mails created without needing to spin up a Linux maker that reports the system status every 5 minutes, the ram-altman. lol job site turns through sample e-mails produced by the script. Kay composes on the site that, “In fairness, he states the remarks were secured of context, published ‘i desire you to have a lot ram’, and briefly passed Ram Altman on X. That makes this script a day-to-day development report.”