This is the same as complaining that my job puts a filter on my work computer that lets them know if I’m googling porn at work. You can cry big brother all you want, but I think most people are fine with the idea that the corporation I work for has a reasonable case for putting monitoring software on the computer they gave me.

European point of view: My work computer and the network in general has filters so I can't access porn, gambling, malware and other stuff on it. It has monitoring for viruses and malware, that's pretty normal and well understood need to have. BUT. It is straight up illegal for my work to actively monitor my email content (they'll of course have filtering for incoming spam and such), my chats on teams/whatever and in general be intrusive of my privacy even at work.

There's of course mechanisms in place where they can access my email if anyting work related requires that. So in case I'm laying in a hospital or something they are allowed to read work related emails from my inbox, but if there's anything personal it's protected by the same laws which apply to traditional letters and other communication.

Monitoring 'every word' is just not allowed, no matter how good your intentions are. And that's a good thing.

I don't have answer for you, but Alec over at Technology Connections made a video few days ago related to the topic. That might not have the answer for you either, but as his videos (and there's a ton of those, even for refridgerators) are among of the best at youtube that is worth cheking out.

But as a rule of thumb, new materials and hardware are better on pretty much every metric. And if your current one doesn't work properly anymore it'll most likely uses way more power than it should, as coolant flow/insulation/something isn't in fully working condition and thus compressor needs to run more often than on a new unit.

Medvedev found keys for the booze cabinet again? They seem to happily forget the fact that Moscow is well within reach of multiple Nato countries by now. Obviously a ton of things need to change before anyone with a gun is standing on a red square, but Finland, Sweden, Estonia and Poland (among others) are quite capable of hitting the Kreml (in theory, and in practise if needed) with fighter jets in less than 30 minutes. Additionally their ports opening to gulf of Finland are in reach of both Finns and Estonians with traditional artillely, and at least we in Finland are pretty capable and accurate with our hardware.

So, even if they find some old soviet relic still functional, Nato has multiple options to level multiple cities at Russia before their missile hits the ground. Nuclear attack against Ukraine would of course be a humongous tragedy with terrible price on civil casualties, but I'm pretty confident that it would be the last thing the Russia we currently know would do as a country.

Yep. I'm running 1/1Gbps wan connection over cat5e just fine. Even on very noisy environment at work with a longish run (70+ meters) we ran pretty damn stable 1/1Gbps over good quality cat7.

Didn't read this article, but the pregnancy test doom was "just" a microcontroller with oled display shoehorned inside pregnancy test case. So, if that counts then you could make a rock or concrete slab to play doom.

According to minusrus they've lost 7193 tanks out of 3300 Russia had before the war started. I sincerely hope that the article is correct, but so far they've been able to replace lost hardware with a decent rate with manufacturing and presumably purchasing from their allies.

One can hope that the current massive attack ends with the Swan Lake on Russian tv's, but right now I'm more worried if Ukraine can hold the lines long enough for that to happen. They really need reinforcements, it's pretty difficult to fight a war without ammunition.

Dd. It writes on disk at a block level and doesn't care if there's any kind of filesystem or raid configuration in place, it just writes zeroes (or whatever you ask it to write) to drive and that's it. Depending on how tight your tin foil hat is, you might want to write couple of runs from /dev/zero and from /dev/urandom to the disk before handing them over, but in general a single full run from /dev/zero to the device makes it pretty much impossible for any Joe Average to get anything out of it.

And if you're concerned that some three-letter agency is interested of your data you can use DBAN which does pretty much the same than dd, but automates the process and (afaik) does some extra magic to completely erase all the data, but in general if you're worried enough about that scenario then I'd suggest using an arc furnace and literally melting the drives into a exciting new alloy.

Bare feet are a bit clickbaity on the headline. That alone doesn't mean much, but when it happens on a area where you should have full protective gear at the (supposed to be) sterile part of the manufacturing it's of course a big deal. But it would be equally big deal if you just stroll there in your jeans and t-shirt with boots you stepped on a dog shit on your way to work. And even then it's not even close of being the biggest issue on manufacturing where they constantly ignored all of the safety protocols, including ignoring test results which told them that the product is faulty.

I don't know what to pick, but something else than PDF for the task of transferring documents between multiple systems. And yes, I know, PDF has it's strengths and there's a reason why it's so widely used, but it doesn't mean I have to like it.

Additionally all proprietary formats, specially ones who have gained enough users so that they're treated like a standard or requirement if you want to work with X.

DNS is a quite well matured technology and it's just as complex as it needs to be and not a bit more. It's a very robust system which has been a big part of the backbone of the internet as we know it today for decades and it's responsible for quite a large chunk of stuff working as intended globally for millions and billions of people all day every day.

It's not hard to learn per se (it's something you can explain on a basic level to every layman in 15 minutes or so), it's just a complex system and understanding complex systems isn't always easy nor fast. Running your own DNS-server/forwarder for a /24 private subnet is rather trivial thing to do, but doing it well requires that you understand at least some of the underlying tehcnology.

You really need to learn how to walk at first and build on that to run. It's just a fundamental piece of technology and there's no shortcuts with it due to nature of DNS services. You can throw whatever running on a container by following step-by-step instructinos and call it a day, but that alone doesn't give you the knowledge to understand what's going on under the hood. That's just how the things are and should I have my way with things, that same principle should apply to everything, specially if it's going to face the public internet.

Which is a lot more difficult in every aspect than just throwing a single line on crontab and calling it a day.