I think the hard-right people have mostly self-exiled to their own echo chambers like truth.social and other places that are Donald-used-and-approved. I think he’s also active on Twitter again now that Musk has destroyed all content moderation on the platform. They follow their great leader and unless and until he starts posting his demagoguery on Lemmy they have no interest and no reason to come here.

It’s not difficult it’s just expensive and energy intensive, and frankly boiling water is both cheaper and easier and we’ve had lots of experience doing it in massive quantities since the steam age and it works great and gives off steam or hot water which can be used for lots more stuff like heating and even power generation. Ice is almost useless in comparison.

As for why you can’t freeze salt into ice, they don’t mix. It’s like trying to mix oil and water. Technically, if you get the ice really really cold and mash it up with some equally cold salt you could make some kind of mixture of ice and salt and maybe even compress it together until it forms a solid mass again, but it’s not saltwater ice, it’s just salt and ice mixed together like oil and water. They may appear mixed, but they don’t mix, they don’t dissolve into each other. Ice’s crystal structure does not have anywhere for the salt to go and the salt’s crystal structure doesn’t have anywhere for the ice to go they’re not compatible in any way.

Matrix and its implementations like Synapse have a very intimidating architecture (I’d go as far as to call most of the implementations somewhat overengineered) and the documentation ranges from inconsistent to horrific. I ran into this particular situation myself, Fortunately this particular step you’re overthinking it. You can use any random string you want. It doesn’t even have to be random, just as long as what you put in the config file matches. It’s basically just a temporary admin password.

Matrix was by far the worst thing I’ve ever tried to self-host. It’s a hot mess. Good luck, I think you’re close to the finish line.

Most cheap non-dimmable LEDs have drivers that use resistors to determine the current to drive through the LEDs. As a rule, these are always set too high to overdrive the LEDs (sometimes as much as twice their rated current) for marginal brightness gains and to burn out the bulb prematurely. I’m obviously unable to actually see directly into the operation of the great minds that design LED lightbulbs but logic leaves me with only those two plausible conclusions, I’ll let you decide which motivation you think is a bigger factor for most manufacturers.

Conveniently, most manufacturers carefully fine-tune this value to prematurely destroy the LEDs at just the right time, which requires careful balancing of resistors, and even MORE conveniently (for us) the cheapest way for them to do this is typically to use two resistors. And MOST conveniently (for us), if you were to carelessly break one of the pair of resistors they use, and leave the other one intact, the current would immediately drop to a very reasonable and appropriate level, generating much less heat, drawing much less power, making LED death extremely unlikely, and only modestly reducing brightness in many cases, because LEDs have non-linear brightness and the heavily overdriven ones are typically FAR beyond the point of diminishing returns. In some cases the reduction in power results in basically no visible difference in light output. In some cases it can be argued they’re literally stealing extra power from your electricity bill and using it as an electric heater for no purpose other than to burn out your own light bulbs prematurely so you have to replace them.

The good news is, like I said, removing one of the responsible resistors instantly solves the design flaw and is usually quite easy even without any special tools or electronics knowledge. BigCliveDotCom calls this “Doobying” the bulbs after the Dubai bulbs that were mentioned in other comments. If you watch some of his videos about LED bulbs you should be able to see the pattern of which resistors to remove, if they are on the board they will basically always be right next to each other and relatively small values (typically in the 20 ohms to 200 ohms range). The only modification I make to his procedure is that I prefer to remove the HIGHER value of the two resistors instead of the lower one, which results in perhaps somewhat less lifetime preservation (still much more than the original setting) and less power savings, but more brightness, and is usually adequately good for my purposes. I also use sturdy tweezers to remove the resistor instead of a screwdriver which seems to me that it would have a higher risk of collateral damage.

Is it a lot of work for a single light bulb? Kind of, yes. But once you get it done a bunch of times, you’ll probably rarely have to do it again, as these bulbs last almost forever. In fact, I have yet to have one actually fail, I am mostly just replacing the occasional old unmodified LED bulb from time to time.

This will not work with dimmable bulbs or certain fancy high end bulbs. Also some are much, much easier to modify than others. Clive calls the ones that are relatively easy “hackable” and it’s really a crapshoot to find them. Some have covers/bulbs/diffusers that are nearly impossible to remove without catastrophic damage to the bulb and/or your hands. Others simply use a different circuit design that doesn’t have resistors. Some only have a single resistor, meaning to change the value you need to solder a new one in its place. In my experience, the bargain-basement, junkiest, least reliable bulbs tend to be the easiest to hack this way and often skimp on things like “gluing the lens on” so it’s easy to get off. But you’ll have to experiment to find a brand and style that works well for this.

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.

While it sounds a bit hacky, I think this is an underrated solution. It’s actually quite a clever way to bypass the whole problem. Physics is your enemy here, not economics.

This is kind of like trying to find an electric motor with the highest efficiency and torque at 1 RPM. While it’s not theoretically impossible, it’s not just a matter of price or design, it’s a matter of asking the equipment to do something it’s simply not good at, while you want to do it really well. It can’t, certainly not affordably or without significant compromises in other areas. In the case of a motor, you’d be better off letting the motor spin at its much higher optimal RPM and gear it down, even though there will be a little loss in the geartrain it’s still a much better solution overall and that’s why essentially every low speed motor is designed this way.

In the case of an ammeter, it seems totally reasonable to bring it up to a more ideal operating range by adding a constant artificial load. In fact the high precision/low range multimeters and oscilloscopes are usually internally doing almost exactly the same thing with their probes, just in a somewhat more complex way behind the scenes.

I still use Nextcloud for syncing documents and other basic stuff that is relatively simple. But I started getting glacial sync times consuming large amounts of CPU and running into lots of conflicts as more and more got added. For higher performance, more demanding sync tasks involving huge numbers of files, large file sizes, and rapid changes, I’ve started using Syncthing and am much, much happier with it. Nextcloud sync seems to be sort of a jack of all trades, master of none, kind of thing. Whereas Syncthing is a one trick pony that does that trick very, very well.

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.

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.

That’s what LCARS means, it’s the name of the computer console in Star Trek. In the show, it stands for “Library Computer Access and Retrieval System” although it’s often used for stuff other than the library computer too.

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.

They’re only lying as long as people can continue to over and over find their way around the obstacles they place in the way, and it gets harder all the time. They have more money and more resources and more organization than the hackers trying to defeat them, they’re winning the war of attrition. We may be able to make small breakthroughs here and there, but overall we continue to lose more and more territory, because the amount of effort is disproportionate to the goals. Most of what’s left of the custom ROM community has given up on the losing battle with manufacturers and providers and changed focus to the various freephones but even they have their own troubles and are fragmented and short-lived. Between carriers, manufacturers, and content providers the whole mobile ecosystem is designed to be impenetrable. It is intentionally a fortress full of deadly traps and open source supporters have no hope to breach it anytime soon.

Never had a single functional problem with Nextcloud, other than the fact that it’s oppressively slow with the amount of files I’ve shoved into it. Mind you I also don’t use MySQL/MariaDB which I consider a garbage-tier DB. Despite Postgres not being the “Recommended DB” for Nextcloud it works perfectly for me. Maybe that’s the difference.

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.

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!)

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.