So it’s not really FOSS at all, it’s just a loss-leader to draw you into the network, trap your data, and then enshittify and monetize as per standard practice.

I feel like you are the one who is confusing a “NAS device” or “NAS appliance” as in a device that is specifically designed and primarily intended to provide NAS services (ie, its main attribute is large disks, with little design weight given to processing, RAM or other components except to the extent needed to provide NAS service), and a NAS service itself, which can be provided by any generic device simultaneously capable of both storage and networking, although often quite poorly.

You are asserting the term “NAS” in this thread refers exclusively to the former device/appliance, everyone else is assuming the latter. In fact, both are correct and context suggests the latter, although I’m sure given your behavior in this thread you will promptly reply that only your interpretation is correct and everyone else is wrong. If you want to assert that, go right ahead and make yourself look foolish.

Joke’s on Reddit, I’ve always been posting unhinged misinformation.

You can also automate this with autossh which is designed for exactly this kind of persistent tunnel. Although a simple “while” loop might seem like the intuitive way to keep it running, autossh is very reliable and takes care of all the corner cases for you.

Keep the gray plastic. Remove black clip around the vertical wheel post in the gray plastic. Remove wheel and wheel post. Buy new wheel. Installl new wheel. It will be easier to find a new wheel once you have the old wheel out so you can take measurements. but it’s likely something pretty standard, off-the-shelf. Wheels are something that companies buy, they rarely build them themselves. They typically come as a castoring assembly with wheel, axle, spindle, and attachment post in a variety of common sizes and with a dizzying variety of actual wheels.

a) Forecasts are very resource-intensive, they are performed on a specific schedule using a computational forecast model. Updating the predictions would require inputting new data and running the model again, and by the time they do that, the next forecast will already be out.

b) Do they know it’s wrong? Where did you get the temperature? From an official weather station? If not, there is no reason to imagine that someone is noticing that this one particular model run was wrong in one particular spot across the whole country and trying to fix it in real time.

c) If you did get the current temperature from an official weather station, that IS your update for it. Real time data from official weather stations is always going to trump the forecast model. What would be the point of updating the forecast when the current measured data from the weather station is now available? That’s like driving down the highway and saying “I was predicting my speed would be close to 65mph, but due to the heavy traffic I’m seeing today, I’m going to re-estimate my speed to be 45mph” when you have a perfectly accurate speedometer right in front of you telling you exactly what speed you are going at all times. Forecasts are only useful for the future, and they can be wrong.

Nah, I wanted to love NixOS, and granted it seems like a perfect fit for my recommendation, but a bunch of things about it rub me the wrong way. It’s just not for me. I’ve always been most comfortable with Debian and that’s what my setup script is designed for. Lots of apt.

I would need to factory reset the whole server for that, which would be … highly inconvenient for me. It took me quite a long time to get everything working, and I don’t wanna loose my configuration.

This is your actual problem you need to solve. Reinstalling your server should be as convenient as installing a basic OS and running a configuration script. It needs to be reproducible and documented, not some mystery black box of subtle configurations you’ve forgotten about ages ago. A nice, idempotent configuration script is both convenient and a self-documenting system for tracking all the changes you’ve ever implemented on your server.

Once you can do that, adding whatever encryption you want is just a matter of finding the right sequence of commands, testing it (in another docker perhaps) and then running your configuration script to migrate your server into the desired state.

$400 is pretty steep. That is probably more than a lot of the computers this would be plugged into.

I can’t live without my Nextcloud + Email server. Having all my personal files, contacts, email, calendar, and other personal information immediately accessible synced and backed up with a single app on any device or platform I want to use, is a dream come true, and I get to do it without any Big Tech, avoiding their lock-in and privacy invasion and without any fees or limits beyond my own hardware.

OpenVPN is how I can access it from anywhere in the world, so that gets an honorable mention too.

It’s veeeeery not standard in Canada. I use it on my phone and most people who see it on the lockscreen treat me like I’m an alien, and it’s about a 50/50 mix of people who simply think 24 hour time is weird (but at least recognize it) vs. people who seem genuinely baffled by the digits they see appearing on my phone and don’t even seem to recognize it as a time at all.

A Dockerfile is basically just a script that starts a container image (ranging from standard Linux OS installs like ubuntu or debian or alpine to the very specialized pre-made containers with every piece of software you want already installed and configured and everything unnecessary stripped away) and then does various stuff to it (copies files/dirs from local, runs commands, configures networking). It’s all very straightforward, and if you know how to write a bash script or even just a basic batch file that’s pretty much all its doing, and the end result is a container, which is basically a miniature Linux virtual machine (that is supposed to be “single purpose” but there’s no technical limitation forcing it to be)

The simplest way to create a container is to use a standard OS container as I mentioned and install the software you want exactly as you normally would in that OS, using the OS package manager if you want, following tutorials for that OS or installing manually using the instructions from the software itself. Either way should work fine. Again, it’s basically not much different from having a virtual machine running that OS. You can even start up a root bash prompt and install it that way if you prefer, or even connect over ssh by running an sshd server on it (although that’s totally uneccessary and requires extra work).

For basic Dockerfile syntax, look at other people’s Dockerfiles and realize you probably don’t need 90% of the more complex ones. There are millions of them out there, you should be able to find some simple straightforward ones and just mimic those. Will you run into “gotchas”? Sure you will, Docker is full of them, and when you do your Dockerfile will get a little more complex as you find a way to deal with the problem Docker has created for you. Here’s a pretty simple tutorial example of a Dockerfile that just installs a bunch of packages from Debian and doesn’t even run any specific services, or alternatively here’s a Dockerfile that does nothing but run and configure an ssh server like I mentioned above (again that’s totally unnecessary normally but the point is you can certainly do it if you want to!)

No good reason, just historical inertia and resistance to change. People stick to what they’re familiar with, either the imperial system or to common metric units. Making a “metric ton” similar in size to an “imperial ton” arguably helped make it easier for some people to transition to metric.

Megagram is a perfectly cromulent unit, just like “cromulent” is a perfectly cromulent word, but people still don’t use it very often. That’s just how language works. People use the words they prefer, and those words become common. Maybe if you start describing things in megagrams other people will also start doing it and it will become a common part of the language. Language is organic like that, there isn’t anyone making decisions on its behalf, although some people and organizations try.

I don’t think they know about metric prefixes, Pip.

Imagine if the marketing people discovered that they could advertise that it has 19 million uWh (in Doctor Evil voice). Don’t say it too loudly though, someone at Apple might hear.

If you can prove beyond any reasonable doubt that someone is ignorant of facts, and then sure you can call it obvious and good. But when nobody can agree what is reasonable, why is your perspective of good the one everyone must follow? It’s not always obvious. Don’t pretend it is. And things that are reasonable and obvious to you aren’t necessarily reasonable and obvious to others. You aren’t willing to embrace the diversity of human experience and opinion, so you won’t get the benefits of that diversity. Just because someone else has a different idea doesn’t make it wrong. If you think literally every idea that isn’t exactly the same as yours is wrong, then we’re wasting our time here anyway.

So again, why is your path the one we’re picking? Even if I do agree with it, I am not willing to agree to it blindly, I want to know why we’re supposed to follow your advice/instructions/demands. At gunpoint or otherwise. And that’s why I’ll never follow a totalitarian, because totalitarians never have to explain themselves, and generally won’t. I hope you brought enough bullets if that’s your plan.

I read the title as “NVR hardware for a frigate” and was like WTF kind of self-hosting are you doing with military hardware on a warship.

Now I kind of want a warship.

Musk is the richest man on Earth, give or take a few billion here or there. He can keep it running as long as he wants. It’s nothing but a toy to him. The problem will start when he finally gets bored of it, because he has already broken it to the point that nobody else will want it. He has killed it, it’s just not dead yet as long as he keeps swinging it around and paying its bills. But one day he’ll stop doing that, maybe once he finds a new, shinier toy. We just don’t know when.

Does the change in gravity gradient across your body kill you right now? No? You are currently orbiting the supermassive black hole in the center of the milky way.

It was implied by “accretion disc” and by the fact that we’re talking about gravitational gradients at all that we’re talking about a close orbit. Gravitational strength gets smaller with distance according to the inverse square law, so by the time you’re a few light years out from the galactic core the gravitational gradient is already extremely insignificant.

brb replacing all my bodily fluids with LSD, will let you know how it goes

I’d argue against that. For one thing it is impossible to imagine a situation where there is no change in the gravitational gradient across your body over time. Your orbiting a black hole situation is a perfect example of a situation where the gradient alone would tear you apart. The conditions you’ve specified are tautological. There’s no way to maintain a zero gravitational gradient while also simultaneously having extremely high gravitational field. The two are mutually exclusive in any conceivable scenario.

It’s like saying a human being in a hypersonic wind stream won’t necessarily hurt you, burn you alive and rip you to pieces (not necessarily in that order) as long as there is no turbulence and you have a sufficient boundary layer – but you’re a non-aerodynamic human body in a hypersonic wind stream, so of course there will be turbulence and the boundary layer will not protect you at all, you’re going to die, basically instantly.