First, one must understand that the Federal Reserve was the main trojan horse vehicle for the European banking families into America. Read any number of good books, starting with the latest edition of G. Edward Griffins "The Creature from Jekyll Island".

But all that is mostly known already to those who have payed attention and done the reading... so whats next?

My conclusion is that America is being setup, in multiple ways (fall guy for global empire, etc), but one major setup that is going on right now is a twofer: 1) Jack up the US economy at any time by raising rates and unraveling the ponzi scheme and 2) If you do 1), you have the perfect excuse to try to implement some CBDC-esque new system, but this time with much more surveillance tech, for example unified ledgers that merge digital identity with financial identity, with ESG and social credit style added on. Read Whitney Webb for more on the structures being put in place for this.

So what is happening is that Trump knows the people that control the Fed, for whom the Fed chair is a mere mouthpiece, really want to suddenly and unexpectedly hike rates and soon, but Trump doesn't want it to happen under his last term, so he has been doing major backroom maneuvering to influence the Fed every time a rate-change date is coming up. Essentially he wants to kick the can to the next POTUS, but since the Fed is technically independent, it really can do whatever it wants, all he can do is fire after the fact. My guess is they will drop it on him late term, a perfect excuse to usher in the political pendulum swing of the hegelian game they play with us.

To me, that this backroom maneuvering is becoming more public tells me they really want to do the sudden rate hike.

Want a decent intro to the real fed? Try this video from the great James Corbett: https://www.youtube.com/watch?v=5IJeemTQ7Vk

The same reason you get wierd looks when you say you don't facebook sometimes.

It's like existing outside the control or influence of some $manyuser $app/$website is unthinkable to those who exist within the prison ecosystems. I am a greybeard linux admin moonlighting in windows world, and the state of infra in ms land is baaaaadddd. When I tell engineers though, I get a thousand justifications about why its ok that its this bad (because it was worse before, etc), because the tooling is so bad it gets in the way of accomplishing your goals.

Same mentality... I personally don't really understand it. Either you control your compute or you don't.

Thats who linkedin draws. I used to exclude linkedin resumes when interviewing heavier linux engineering/ops candidates for this reason.

And ufw supports nftables btw. I think the real lesson is write your own firewalls and make them non-permissive - then just template that shit with CaC.

https://www.slingacademy.com/article/git-post-receive-hook-a...

Another of my tricks is to tie in your containerization there too, system-nspawn is what I'm using at the moment, but it can apply to others.

The pivot will be when they starting talking about AGI and it's dangers and how it must be regulated! (/clutches pearls)... right now they are at the "look at AI we need it it's awesome" stage.

So for a long time, I traced most roads in the US back to London... (for example Star Chamber origins)...

After a while though, as I dug into the real history of banking, I realized when William of Orange was installed it was shortly after that the Bank of England was established to take them over the same way they later influenced us (Jekyll Island) to establish the Fed, the main trojan horse for a country being monetary countrol.

So I now understand just like the masons, or intel dudes, etc, many of them are just so compartmentalized they don't know what they are a part of. I now view the UK the same way.

So lets keep following the strings up the chain...

"You win battles by knowing the enemy's timing, and using a timing which the enemy does not expect." - Miyamoto Musashi

I also find myself using nspawn just to isolate apps like firefox, etc.

As a greybeard linux admin, I agree with you though. This is why when someone tells me they are learning linux the first thing I tell them is to just type "info" into the terminal and read the whole thing, and that will put them ahead of 90% of admins. What I don't say is why: Because knowing what tooling is available as a built-in you can modularly script around that already has good docs is basically the linux philosophy in practice.

Of course, we remember the days where systems only had vi and not even nano was a default, but since these days we do idempotent ci/cd configs, adding a tui-editor of choice should be trivial.

The solution is nftables.

The solution is bpf.

The solution is emacs-m-x-butterfly-bpf.

Pass is just a shell wrapper around gnupg, when you run pass some/secret/path, what actually happens is pass constructs and executes a gpg command (e.g., gpg --decrypt ~/.password-store/some/secret/path.gpg) and the output of gpg (the plaintext secret) is piped to pass's stdout.

Most people know this though. What I learned I didn't know before though was this:

Memory Zeroing: after it's used (e.g., copied to a pipe or stdout), GPG's internal memory management aims to zero out those memory regions used as soon as they are no longer needed

Memory Locking: GnuPG also uses mlock() (or equivalent OS-specific calls) to lock sensitive memory pages into RAM. This prevents the plaintext keys and decrypted data from being swapped out to disk, protecting against swap-file forensics or cold boot attacks.

I had been banging my head against bash trying to do those things manually, and ended up with the conclusion it was best to use pass/gpg with the following addendums (from my notes in my skeleton secure bash template):

1. Minimize secret lifetime: Use subshells, functions with local variables, and unset, disable bash history

2. Pipe secrets directly: Pass secrets via stdin or process substitution directly to the consuming program without intermediate variables if possible.

3. Rely on the tools: Use pass, gpg, or KMS CLIs that are themselves implemented in lower-level languages and can (and should) implement these memory protection techniques internally.

ps: keepassxc is the other favorite to use