Damn.. You too?
mb_
Hello fellow homelabber
distcc so you can compile on the faster ones and distribute it
Nerfing things on a PVE game that's supposed to be fun shows a lack of creativity.
You can buff the other things while finding better ways to increase the difficulty, instead of just boosting health and throwing more enemies, but that's the "easy" button.
I think you meant no data cap.
The right thing to whom? Shareholders? (=
It hasn't crashed yet, but I won't be able to test it for a couple weeks (vacation time \o/).
For normal use, it looks like the crash is resolved or, at least, as stable as 6.7 was. Next test is to play Helldivers 2 with the Vulkan backend and see if it crashes or run.
Powercolor, red devil.
Under 6.7 I was able to find some a combination that was usable for a few days.
With 6.8, timeouts would happen within 30 minutes.
I fiddles with sched_job module option and the system seems stable now.
They still have, I replaced my 3070 with a 7900 xtx and the 7900 is constantly freezing with ring GPU errors and drivers completely effing up the system. I have already replaced it twice, and I am using workarounds to not hit bugs, but they happen every few days...
I can't remember all the details, but depending on the CPU you are running you may need some extra configuration on opnsense.
There were a few issues, on my servers, running on older Intel Xeon CPUs, but I eventually fixed them adding proper flags to deal with different bugs.
Other than that, running on a VM is really handy.
I am usually more worried about the phone being in some blacklist or not, this has always been one of my issues with the used phone market.
On to your question - 32% battery health seems pretty bad. I just replaced my s22 ultra that I used quite heavily for the last 2 years, it is at 86% battery Healthy.
There are a few ways to do it, but you don't use caddy for SSH.
Last option is how I run my Gitea instance, authorized keys is managed by gitea so you don't really need to do anything high maintenance.
~git/.ssh/authorized_keys:
/usr/local/bin/gitea:
127.0.0.14 is the local git docker access where I expose the service, but you couldn't different ports, IPS, etc.