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.

You do realize that man pages don't live on the internet? The kernel.org one is the offical project website, as far as I know, but the project itself is very much not for the web presense, but for the vastly useful documentation included on your distribution.

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.

Mullvad (apparenlty, first time I've heard from the service) uses DNS over TLS and I don't think that the current GUI version has the option to enable it. Here's a quickly googled howto from Fedora on how to enable it on your system. If that doesn't help search for 'NetworkManager DOT' or 'DNS over TLS'.

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'd say that single core performance and amount of RAM you have are the biggest issues with running anything on old hardware. Apparently, in theory, you could run even modern kernel with just 4MB of RAM (or even less, good luck finding an 32bit system with less than 4MB). I don't think you could fit any kind of graphical environment on top of that, but for an SSH terminal or something else lightweight it would be enough.

However a modern browser will easily consume couple gigabytes of RAM and even a 'lightweight' desktop environment like XFCE will consume couple hundred MB's without much going on. So it depends heavily on what you consider to be 'old'.

The computer at garage (which I'm writing this with) is Thinkstation S20 I got for free from the office years ago is from 2011. 12GB of RAM, 4 core Xeon CPU and aftermarket SSD on SATA-bus and this thing can easily do everything I need for it in this use case. Browsing the web on how to fix whatever I'm working with at the garage, listen music from spotify, occasional youtube-video, signal and things lke that. Granted this was on a higher end when it was new, but maybe it gives some perspective on things.

Is there way to use a usb wifi card(tp-link) as the reciever and make it work?

No. The mouse is not a wifi device, and as it's a old one I doubt it'll support bluetooth either. So you really need the original dongle.

I ran one for a while. In Finland legislation is a bit different, so I wasn't worried about breaking the law or getting sued, but my ISP got in touch pretty quickly. They were professionals and understood the situation when I explained why my traffic might look "a bit" suspicious and I attempted to clean up bad actors from the traffic with filtering and whatnot, but eventually ISP got enough complaints and they were pretty much forced to tell me that either I shut the exit node down or they'll cut my line.

As I said, they were very professional about it, and managed the whole experiment as good as I ever could have hoped, but my agreement with them has an option that if I'm letting malware and bad actors leave the network even after warnings they can shut the connection down. And that's understandable, I suppose they have similar agreements with other providers and they received all the abuse mail my exit node was causing, so I'm still a happy customer with them even if they eventually took the hard way.

I'm still pretty sure it would be possible to run filtered exit node, but it would require far more time and other resources that I'm willing to spend on a project like that and I'm not sure if a single person is enough for it anyways.

So, yes, do your homework and be careful. Legislation plays a significant part (depending on where you live), but your ISP most likely won't like it either.

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.