but never any ideas on how to defend a computer
I already told you how:
https://groups.google.com/g/bitcoindev/c/FpSWUxItXQsNothing is enforced. That kind of things will be optional. As long as you want to have a full archival node, and store everything, including a lot of spam, then you will just run the official version, with the default settings.
And if you will need to have some spam-resistant node, then you will use a different version, which will be compatible, while also rejecting spam, or at least not storing it permanently (or even not downloading the spam at all, and processing some proofs instead). Your node, your choice.
So, do you have a full node? Do you have a problem, to sync it here and now? Because guess what: people are lazy. As long as nodes are not crashing, as long as disks are big enough, and as long as node operators are not sued, because of broadcasting copyrighted material, and as long as nodes can verify the chain faster, than it is made, then nobody cares. People will start to care about spam, and fix things, when they will be directly affected (and many users from forums or exchanges won't be affected at all, because they already use SPV wallets, or they have many altcoins, and they don't care about Bitcoin as a payment system, but care more about blockchain as a solution for all problems in the world).
So, are you affected here and now, to introduce some solutions? If you are, then you can help to discuss or build some of them. But they won't be globally enforced, because the majority wants to have a spamchain, so the spam-resistant version won't be enforced on everyone, as long as spammers have enough resources to keep spamming, and cooperate with spamming mining pools.
Edit: Again, you would then incentive the more harmful spam, the "fake public keys" spam.
You don't have to download, store, or otherwise process some data, if you don't want to. You can process it once, and then forget about it, and only keep some lightweight proofs on your side. Or: if your security model allows for that, you can just download the proof from another node, and don't bother with downloading the original data at all.
Which is your plan, run Knots?
No, I would stick with the original node, but I want to run it in a more lightweight version. In the past, I had some full nodes. I even had some pruned nodes. But now, I think about setting it up differently, because it seems to be more and more risky, to process all of that spam, and distribute it everywhere in a P2P way.
Also note, that the official client won't force you to use it in the default way. You can do many things. Your node trusts the data you fill it with. Which means, that you can still use a lot of functionalities of Bitcoin Core, without storing the full chain, or even without having the full UTXO database. But does it mean, that everyone should do the same? Definitely not, it is only a path for those, who care about resources, and want to control them better.