![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Yes, thank you for repeating what I just said, and justifying my desire for a nat. I do infact actually know a few things about computer networks and tcp/ip since I spent 7 years writing software to interface with and monitor them.
Yes, thank you for repeating what I just said, and justifying my desire for a nat. I do infact actually know a few things about computer networks and tcp/ip since I spent 7 years writing software to interface with and monitor them.
Except the NAT device will stonewall traffic on every port except the ones I open, for my entire network, and then I can just worry about securing the software listening on those few ports, instead of having to worry about the firewalls on every device I own.
Tldr default nat behavior is a state full firewall.
You apparently haven’t seen the video of a fsd tesla going full speed through the fog towards a train crossing with an active train.
The cars display didn’t even indicate that it thought something was in front of it, and would have happily driven right into the side of this train if the driver hadn’t taken over at the last moment. (Driver was an idiot for using fsd in the fog to begin with) but it shows the cameras can’t handle reduced visibility well currently, they saw the fog and just decided it was open road or clear sky.
Gonna be real here, I’m in tech, there is no fucking way I’m gonna open my PC to the entire fucking internet. Vulnerabilities are everywhere and no code is perfect. Firewalls and nat help stop so many attacks from the start.
Even if ipv6 is common I will assume most implementations will be nat based.
Gotta say though it’s kinda nice when you run an update to be able to tell ah yes KDE apps are being upgraded when you see the wall of Ks
Nah, cell towers often have some kind of backup power good for a couple hours or more, at least in the city where I am. I think I once had an outage last 3 days when a tornado wrecked the local transformer station, and still had cell service the entire time.
If you actually knew anything you’d know that overclockers tend to manually reduce the voltage as they increase the clock speeds to improve stability, this only works up to a point, but clearly shows voltage does not directly influence clock speed.
They aren’t over clocking / under clocking anything with the fix. The chip was just straight up requesting more voltage than it actually needed, this didn’t give any benefit and was probably an issue even without the damage it causes, due to extra heat generated.
They aren’t, it’s more “it’s the EUs fault for forcing us to allow businesses like cloud strike to write kernel level antivirus, because we already have our own.”
Run out, far more frequently than you would imagine.
Yes it was perfect in Wayland till yesterday when I updated and fire fox started crashing with explicit sync errors
Oh sweet not just me then! Hoping this one gets fixed soon
Except since it was an antivirus software the system is basically told “I must be running for you to finish booting”, which does make sense as it means the antivirus can watch the system before any malicious code can get it’s hooks into things.
I do, and if you accidentally skip a version when updating it the stupid thing bricks itself, what kind of stupid software can’t handle multiple make version updates.
Had to manually reset the version it thinks it was at and roll back to a older sticker image and update one version at a time until I caught up.
I haven’t had issues with syncing files on android. File sync is literally the only feature I use, so I should probably look for a simpler solution.
Now upgrading the fucking thing is a nightmare, not sure if me using docker images makes it worse or better though.
So that’s why windows always has the wrong time after I’ve been in my Linux install…
The UUID never fucking changes. It is a hardware level identier use the UUID in your configs and they will work until the day you change drives.
And then you have a great big fuck off stack of documentation you can slap in their face with proof that it’s someone else’s problem.
Unless you aren’t actually pinging all the people you say you are.
Except the C++ “Core dumped” line is telling you it just wrote a file out with the full state of the program at the time of the crash, you can load it up and see where it crashed and then go and look at what every local variable was at the time of the crash.
Pretty sure you can even step backwards in time with a good debugger to find out exactly how you got to the state you’re currently in.
Sure for newcomers to a project like the Linux kernel they have to learn C , because that is what the project is currently written in, but trying to transition the Linux kernel to rust forces people who already are contributing to go and learn rust to be able to continue what they were already doing. And sure you can argue that it’s being done so not everything has to go over at once, but there is a level of rust knowledge required at the interface between the two languages, and that burden is as far as I’ve seen being forced on those long term contributors.
It’s not the same thing.