You don’t have to install drivers or CUPS on client devices. Linux and Android support IPP out of the box. Just make sure your CUPS on the server is multicasting to the LAN.

You may need to install Avahi on the server if it’s not already (that’s what does the actual multicasting). The printer(s) should then auto magically appear in the print dialogs on apps on Linux clients and in the printer service on Android.

On Linux it may take a few seconds to appear after you turn it on and may not appear when it’s off. On Android it shows up anyways as long as the CUPS server is on.

From what I understand OP’s images aren’t the same image, just very similar.

I’m thinking Ctrl+C quits and Ctrl+S is scroll lock is that correct?

Any PC can do that, it’s called “status after power off” or something like that.

Isn’t it fourth?

Mozilla has already shipped strict privacy mode by default in recent versions of Firefox so they’re already a leg up on this.

Google is currently trying to transition people to its own proprietary method of tracking (where the browser itself tracks you) so they would love it if third party cookies were no longer usable for that.

Mozilla has also added a direct tracking feature (anonimized) to Firefox btw. Not sure what their agenda is.

Websites are irrelevant, if third party cookies stop working in major browsers there’s no point in setting them anymore, they’ll be ignored.

Looking through the packages available for OpenWRT I would suggest Tcl, Lua, Erlang or Scheme (the latter is available through the Chicken interpreter). Try them out, see what you like.

I’ve actually tried using PHP on OpenWRT and embedded before. It’s not exactly lightweight, it’s a memory and CPU hog. Keep in mind that the kind of machine that runs OpenWRT might only have 32 or even 16 MB of RAM to work with.

Also, PHP is not the first language that comes to mind when doing data processing and/or functional programming. You can but it doesn’t lend itself well to it.

It’s impossible to tell how meaningful Backblaze’s numbers are because we don’t know the global failure rate for each model they test, so we can’t calculate the statistical significance. Also there are other factors involved like the age of the drives and the type of workload they were used for.

buying more reliable devices can definitely save you time and headache in the future by having to deal with failures less frequently.

That’s a recipe for sorrow. Don’t waste time on “reliability” research, just plan for failure. All HDDs fail. Assume they will and backup or replicate your data.

Any difference you personally experience between the three big brands is meaningless. For any failed HDD you have there’s going to be another person who swears by them and has had five of them running for 10 years without a hitch.

But whatever’s cheaper in your area and stop worrying. Your reliability should be assured by backups anyway not by betting on a single drive. Any drive can fail.

For home setup you don’t care because you should have either redundancy or backup (preferably both).

So that typically means buying the cheapest HDD that’s new and from one of the established brands (Seagate, Western Digital, Toshiba) that’s in the correct size for your needs, and you can afford to buy it at least twice (for the aforementioned backups or redundancy), or even thrice, and replace as soon as needed.

In other words there’s no need to speculate on how long an HDD will last, you simply replace it when needed.

Please also note that HDDs over 10 TB are starting to get increasingly replaced with enterprise models which run hotter and make more noise.

And what do you do when Firefox deprecates v2 too?

Repology artificially reduces the number of packages instead of reporting the actual number. Which I find highly dubious because most packages have a purpose. In particular for repositories like the AUR artificially eliminating packages goes against everything it stands for. Yes it’s supposed to have alternative versions of something, that’s the whole point.

If there wasn’t for this the ranking would be very different. Debian for example maintains over 200k packages in unstable.

That sounds a bit suspicious.

I doubt they intend to mine it. For the Russian state is easier to acquire Bitcoin by hacking wallets than mining, and the plebs can’t afford the electricity.

Trading is trading and they’d be risking sanctions whether they take payment with Swift or Bitcoin.

Depends on the distro, some have started to offer btrfs by default.

This is not a new problem, .internal is just a new gimmick but people have been using .lan and whatnot for ages.

Certificates are a web-specific problem but there’s more to intranets than HTTPS. All devices on my network get a .lan name but not all of them run a web app.

7 was actually surprisingly well optimized. It ran OK on an office PC with 512 MB of RAM and a 512 MHz CPU.

You wouldn’t use it like that because by that time apps like browsers and office were starting to feel restricted by that little RAM to the point you could only run either or. But the OS itself stayed out of the way as much as possible, and if you gave it just a little more RAM (like 1 GB) suddenly you had a usable office machine.