

Heat? Could be overheating and throttling?


Heat? Could be overheating and throttling?
That isn’t exclusively true. Programs can capture SIGTERM and ignore it, or do as they please, SIGKILL is non-negotiable though.
Windows does have an equivalent to SIGKILL as well, in taskkill /F.
r/rust is the same, so much vibe garbage :(


Annoyingly, disk discovery. It refused to use my disks, claiming they didn’t have serial numbers. I could see the serial numbers in the frontend and the console, but their middleware just hated them.
I am using a USB multi-disk drive thing, which didn’t work properly on an old kernel, but it should have been fine with the new kernel.
I reported the bug, which didn’t really get addressed, and then had to build my array using the command line tools (which aren’t documented).


I dunno about recommending FreeNAS (Known as truenas now). It is basically an appliance OS, and unless you are using enterprise level hardware, they want nothing to do with you.
I’m currently using it, but it was a very unpleasant experience setting it up.


You’re not wrong, but the only difference (and time will tell if its sufficient), is that they intentionally and explicitly use the free tier for advertisement, so killing that kills their reputation overnight.
But if all else fails and they try to enshitify, their apps are BSD licenced on github, and headscale is adequate, so the free tier would just shift to headscale and carry on.


Thank you [Honorary] Pedantry :D. “ad” just felt wrong somehow, but you are correct. I have fixed it, sorry for the pain and suffering I caused you :D


Honestly, this might be good for the ad industry. Force them to get to the point quicker. Alternatively, we could see a return of epilepsy inducing flashing ads…
I like the idea of IRL billboard ads being “dismissable”. If the ad is too obnoxious, someone gets to press a button and wipe the billboard.


Early in the GNOME /wayland transition, there was a bug I hit where you could drag windows off the edge of the screen, and somehow the desktop would scroll. It was kinda cool conceptually, but completely broken functionally, as it was hard to scroll back.
Edit: Wayland was actually the solution, Xorg was the problem:
https://programming.dev/pictrs/image/bc70285d-88ac-42aa-80be-b8b8f012547b.png


Crowdsec does not provide DDOS protection in the same manner as Cloudflare. You can use crowdsec to block the traffic at your server, but it has already reached your server, and will be using up your ingress bandwidth regardless. So if you were DDOS’d, your site will go down.
Cloudflare prevents the traffic ever reaching your server, while allowing the legitimate traffic through. They block it on their servers, which have much higher bandwidth than any VPS provider has.


I hear you, I host lots of stuff. But none I can think of would be RCE vulnerable directly from a CPU vulnerability. You could use a CPU vulnerability to privesc later, but once someone has RCE, your already pwn’d, and privesc is mostly a given anyway either way. So CPU vulnerabilities falls way down the list of things to worry about.
As long as you keep your router OS patched and up to date, CPU vulns really arent a concern.


I can’t think of any typical services that you’d run on a router/home server that allow arbitrary code execution. The main risk was mostly web browsers with JavaScript, or VPS providers.
Either way, definitely unlikely for a home router.


The beauty of game dev, is that you can make the most cursed codebase, and as long as it works, the only person itll impact is yourself.
Also, startup costs are basically zero, there is no need for a top end PC, whatever you have now is probably good enough to start.


Exploiting those vulnerabilities via pure network traffic is borderline impossible. Most CPU exploits (meltdown et al.) require execution on the device, you can’t do it via crafted network packets.


https://cameroncros.github.io/wifi-condom.html
This is my travel router setup, might be useful for you to start from.


Probably, but raspi only has one interface, and USB network cards can be flakey. You’ll also not get outstandingly fast speeds, so ifnyour on a fast fibre connection you’ll struggle to hit the full speed.


Its a bad idea from a power consumption POV, your old PC will be very inefficient, and running it 24/7 as a router will rapidly add up.
Security wise, you’ll be running a fairly up to date Linux or BSD based OS, so its perfectly safe.
That is a strong stance. What about clip on earings?
Ah, I thought the timeline between the events and the slowdown were a lot closer, and that unplugging the monitor just gave it enough time to cool down.
The monitor part is definitely odd, is it a particularly high res/Hz monitor?
Otherwise I’m also leaning towards excessive swapping being the culprit, but that doesn’t explain the monitor part.