sometimes swap seems to accumulate even though there is plenty of ram. It is too "greedy" by default, probably set for desktops not servers in mind.
Therefore it is better to always tune "vm.swappiness" to 1 in /etc/sysctl.conf
You can also configure your web server / TCP stack buffers / file limits so they never allocate memory over the physical ram available. (eg. in nginx you can setup worker/connection limits and buffer sizes.)
this is the same thing with wifi. There are different channels and transmission power rules depending on country. Something you cannot change even if you are root or build your own kernel, as it's built in to the wifi hardware (eg. raspberry pi)
The US is not defending Taiwan for the sake of "supporting its people" it or because of TSMC. It's actually because Taiwan is part of the "First island chain", and it's crucial in keeping China away from taking the Pacific Ocean and threatening the US west coast. The US will throw everything it has to defend it. It is absolutely vital to US territorial security. See https://en.wikipedia.org/wiki/First_island_chain
my pixel 2 is still rocking too, what an amazing device! (although it now I only use it for flappy bird..)
Highly disappointed that Google stopped updates a long time ago.
another perspective is that WW1 hasn't ended, and ww2 was actually WW1. Even now, if you look at the Ukrainian conflict from an economic perspective, it's a continuation of the same conflicts of ww1
Not quite. WW1, and its continuation WW2, was a fight between Germanic states on one side vs. Britain and France on the other side. The fight ended (it really ended!!!) when two powerful outsiders (US and USSR) invaded and split the European continent.
What is happening now in the Ukraine is a result of a gross miscalculation without any grounding in reality (no, NATO was not going to attack Russia). The war in the Ukraine is not a leftover from WW2.
Jupiter and Saturn moons always make inspiring hostnames. Right now, I have Callisto, Europa, and Ganymede. Ganymede has the most powerful setup. Yesterday, I decommissioned Io.
I never made a Dockerfile in my life, so I thought it would be faster just getting o3 to point to the GitHub repo and let it figure out, rather than me reading the docs and building it myself.
I spent hours debugging the file it gave me... It kept on adding hallucinations for things that didn't exist, and removing/rewriting other parts, and other big mistakes like understanding the difference between python3 and python and the intricacies with that.
Finally I gave up and Googled some docs instead. Fixed my file in minutes and was able to jump into the container and debug the rest of the issues. AI is great, but it's not a tool to end all. You still need someone who is awake at the wheel.
Pro-tip: Check out Claude or Gemini. They hallucinate far less on coding tasks. Alternatively, enable internet search on o3 which boosts its ability to reference online documentation and real world usage examples.
I get having a bad taste in your mouth but these tools _aren't _ magic and do have something of a steep learning curve in order to get the most out of them. Not dissimilar from vim/emacs (or lots of dev tooling).
edit: To answer a reply (hn has annoyingly limited my ability to make new comments) yes, internet search is always available to ChatGpT as a tool. Explicitly clicking the globe icon will encourage the model to use it more often, however.
most likely "shell access" was confused with execution of "shellcode" which is a type of code, typically bytecode, that gets injected by the hacker and the server gets tricked into executing it. Once it's executed, it can do anything, leave new files, open ports, disable firewalls, change the admin password, etc
Shellcode is usually weirdly formed native machine code, typically written in a "return-oriented programming" style, that can be inserted with a buffer overflow and somehow jumped to. But usually not bytecode.
It was not - attacker ran an exploit that have him a remote shell access. No shellcode was involved (that's for binary exploits which is not what happened here)
Therefore it is better to always tune "vm.swappiness" to 1 in /etc/sysctl.conf
You can also configure your web server / TCP stack buffers / file limits so they never allocate memory over the physical ram available. (eg. in nginx you can setup worker/connection limits and buffer sizes.)