>slowing M2 growth to near zero and eventually reversing it.
The M2 money supply went from 15.4b at the start of 2020 to a peak of 21.7b, before slightly reversing to 20.7b. Then they just continued printing. Now it currently stands at a record high of 22.2b. The dollar is more diluted than ever.
its a tight rope. shrinking the money supply also has downsides.
Summary of the Policy Reversal
Period Policy Action Balance Sheet Impact
June 2022 – Nov 2025 QT (Tightening) Shrank from ~$9T to ~$6.5T
Dec 1, 2025 QT Ends Runoff stops; maturing assets reinvested
Dec 12, 2025 – 2026 Reserve Management Expansion begins via T-bill
purchases
By December 1, 2025, the Fed officially halted QT after reducing its balance sheet by approximately $2.4 trillion. The following factors forced the reversal to expansion:
1. Liquidity Squeeze and Repo Market Stress
As the Fed drained cash from the system, bank reserves fell toward "critical thresholds". This caused stress in the overnight repo market, where banks lend to each other.
Spiking Rates: Key short-term lending rates, such as the Secured Overnight Financing Rate (SOFR), spiked above the Fed’s target range, indicating cash was becoming scarce.
>No doubt in the hope of making people mad at the EU.
We should be mad at the EU. They could have easily written a clause into the law saying companies must respect the Do-not-track header from the browser. But for whatever reason, they chose not to.
It actually proves that they _don't_ (or didn't) have that kind of access because they first publicly asked for the access and then rescinded that request when they, not officially but widely accepted, acquired access through some kind of hack/bug/exploit given to them by, probably, the IDF or an Israeli private company.
It’s normal if you use the Nvidia proprietary driver. Every notification leaks one fd, so if you get a lot of notifications it’ll segfault once or twice per day.
It is normal for KDE. KDE is mockingly called KrashDE in Linux circles for a reason. We're only 4 days into 2026 and there's already dozens of crash-related bugs filled in the bug tracker: https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_...
Yes, KDE aggressively caches and indexes things by default whenever you have free RAM unless you disable this behavior in multiple places in multiple applications. For example, in Okular you can tune it to choose how much of a pdf you want to keep rendered in memory, if you have a tonne of memory, this makes it the smoothest pdf viewer I have ever used.
It has become reasonable graceful in giving it back when you you need it nowadays.
The Linux kernel does this too, yet it does not crash like KDE. At any given moment, most of your free RAM is used to cache stuff by the kernel, unless you've recently rebooted.
No, what the Linux kernel does instead is randomly kill user processes :)
It's kinda infamous for that, and had held up Linux adoption for a decade or so.
But you sort of missed the point, I think. The comment chain was about speculating why KDE could possibly crash if there was faulty RAM while other software would be fine. And the kernel absolutely crashes when there's faulty ram.
The M2 money supply went from 15.4b at the start of 2020 to a peak of 21.7b, before slightly reversing to 20.7b. Then they just continued printing. Now it currently stands at a record high of 22.2b. The dollar is more diluted than ever.
https://fred.stlouisfed.org/series/M2SL