Not exactly self-hosting, but I've worked at two different academic labs that had unique issues and small budgets.
The first was on top of a mountain at 3km elevation. The low air pressure meant that all hard drives had a lifespan of no more than a year before starting to have issues. This was in the pre-SSD days. The "solution" was to boot from a floppy, never compress data, and have a student return the drives to a low elevation and swap them for the prior ones every six months.
The second was at a place that was using old Datacube MaxVideo hardware that we would never have the budget to replace. It would crash if the room temperature got above about 18C, so we set the thermostat to 15C. Which doesn't sound too bad until you've tried sitting at a desk for 8 hours where everything is 15C and the heat is just slowly leaving your body into the chair, the desk, and the keyboard. And then you walk outside where it is 32C and instantly start sweating because you're still in several layers and fingerless gloves.
I have a NAS that had a similar problem, every week or two it would stop responding. From the logs it was clear that the machine was running fine after going non-responsive, but either the NIC or something else network related was crashing. However, the logs weren’t capturing the exact issue. I wrote a script to ping Google every 10 minutes, write a bunch of debug data to disc if it failed, and then reboot.
And it has never happened in the year since. I have no idea what the root cause was, but sending those pings out seems to have fixed it.
oh they definitely cause some, but not nearly as much as the wing breaking because you’ve concentrated the stress into two small areas, or from having to add so many rotors inside the wings that they’re just one rotor next to another.
Take a look at a top down picture of one to get an idea of the swept rotor to wing area ratio. The swept rotor area is almost twice the wing area. If all those rotors were inside the wings, there wouldn’t be any wings left.
I use Tailscale for this, with my own Headscale server so that I am in control of everything. It’s a much easier approach that is more likely to pass the spousal acceptance factor.
Thats kinda the point of the malicious compliance though. It’s an optional field. By default, distros can choose to ignore it or auto fill in 1900-01-01. In places where it’s required by law, adduser can ask and it will accept anything. The same way adduser currently asks for your real name, phone numbers, and room number but does not give a fuck what they are or if you fill them out.
The parental controls issue is actually a bigger deal. I would love to give my kids a Linux laptop that could actually protect their privacy while also giving me good parental control tool, but such a thing does not exists. Yes, if you do a quick search for “Linux parental controls” you’ll find some things, but they are clearly half-assed attempts that don’t really work. This absolutely doesn’t either but maybe it’s a step in that direction. Instead, I do what most schools and parents do and give them a Chromebook because it has a good, though not great, parental control system.
Let me be clear, I am also opposed to age verification laws and have written, called and had meetings with my representatives to oppose them. It’s been somewhat successful, though not as much as I would like.
In the end, malicious compliance that allows FOSS developers plausible deniability is better than ignoring the laws and hoping that you’re not the one they decide to make an example of.
No, RAM speed has almost no real-world non-benchmark impacts outside of extreme overclocking. In basically every case where you would start to see the difference, just adding more RAM will make a bigger one.
You mean the change that was writen as an act of malicious compliance, by someone opposed to age verification laws, in such a way as to make an easy end run around them for all Linux developers, but then everyone went off half-cocked and started sending the author death threats? That compliance?
I think the real issue with the modern terminal, and Linux in general, is that we are using tools designed for programmers and system admins, who are expected to know exactly what they are doing, to build and run servers and treating them like they are end user tools. My grandmother was perfectly happy using a terminal for the only computer she owned because the tools it provided were simple and had those built in protections in a way that bash never will be.
I’ve been following sea ice extent for a long time and the number one thing I’ve learned is to not get caught up by any given blip. Sea ice is a complex, slow moving system, so any wobble on the line in a given year is basically meaningless. Look at the year to year and decade to decade trends.
I’m going to echo what others have said here but hopefully clarify it somewhat. For most FOSS projects you can contribute by code, documentation, writing/reviewing bug reports, or other project management tasks. The projects probably have a “Contributing” section on their website that will help you get started and might even have an “easy tasks” or “good for beginners” section.
If you’re primarily interested in contributing by writing code, then you need to learn to code. Pick a language that a project you care about is written in and find the beginners tutorials.
You going to want to learn the basic tools the project uses even if you’re not writing code just so you can interact with the project’s community, so probably git, their bug tracker, and whatever they use for documentation and translation.
And don’t be surprised if it takes a while to get that first contribution in. FOSS developers tend to become grumpy with time and generally have high standards, and due to the massive amount of LLM slop being thrown their way these last few years have often become even more so. But your work will be appreciated if you stick with it.
Heck yeah they did! I remember going over to my grandmothers house to use Word on her computer running DOS. She used that computer to keep her personal budget, do the accounting for her office supply business, write letters, and the newsletters for her church and social clubs. No gui, just a command line and some things that we would now call a TUI.
um, no. The joke is that a lot of people are scared of Linux because they think it’s “just a black screen with a bunch of text”, a lot of people who are newly using Mint or the other common “friendly” distros are proud and trying to convince everyone that you never need to touch the command line, and then the more people know what they’re doing the more likely they are to just live in a terminal and not bother with anything else.
I… what are you talking about? Those words make sense on their own and I could probably diagram them as sentences, but put together in that way they don’t seem to parse into anything coherent.
Edit: Wait, are you saying that you think there are distros that don’t have a terminal or terminal emulator?!?
That's quite right, which is why nwipe (the core tool of ShredOS) has a different mode for SSD vs HDD.