cecilkorik

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.

It is mostly a myth (and scare tactic invented by copyright trolls and encouraged by overzealous virus scanners) that pirated games are always riddled with viruses. They certainly can be, if you download them from untrustworthy sources, but if you're familiar with the actual piracy scene, you have to understand that trust is and always will be a huge part of it, ways to build trust are built into the community, that's why trust and reputation are valued higher than even the software itself. Those names embedded into the torrent names, the people and the release groups they come from, the sources where they're distributed, have meaning to the community, and this is why. Nobody's going to blow 20 years of reputation to try to sneak a virus into their keygen. All the virus scans that say "Virus detected! ALARM! ALARM!" on every keygen you download? If you look at the actual detection information about what it actually detected, and you dig deep enough through their obfuscated scary-severity-risks-wall-of-text, you'll find that in almost all cases, it's actually just a generic, non-specific detection of "tools associated with piracy or hacking" or something along those lines. They all have their own ways of spinning it, but in every case it's literally detecting the fact that it's a keygen, and saying "that's scary! you won't want pirated illegal software on your computer right?! Don't worry, I, your noble antivirus program will helpfully delete it for you!"

It's not as scary as you think, they just want you to think it is, because it helps drive people back to paying for their software. It's classic FUD tactics and they're all part of it. Antivirus companies are part of the same racket, they want you paying for their software too.

Godot is looking much better to me today than it did yesterday.

It's possible he's always been this much of an idiot and has only managed to succeed to where he is by sheer dumb luck and the principle of failing consistently upward.

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 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.

Call the local fire department non-emergency number and ask if they can schedule a visit to inspect your fire alarms and provide recommendations on the situation. The fire department is genuinely interested in your safety, because it's also important for their safety so they don't have to come rescue you. If anything is a fire hazard, the professionals can explain why and explain how to fix it. But they'll probably say "WTF" because the landlord is most likely just being a fuckface, as landlords do. Assuming the latter, ask them if you get the "WTF" in writing so you can wave it in the landlord's face when you tell them to fuck off and die.

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.

Owncloud is not fully open source. Nextcloud is. They have developed in different directions since then, but that remains the fundamental difference that split them apart in the first place. If that matters to you, Nextcloud is the right choice. If that doesn't matter to you, then use whichever you prefer and has the features you need.

It is. The web was eventually corporatized and the corporations sucked all the air out of the room suffocating anything too small to compete. The fediverse is, if not taking it back, at least opening a space for those who don't want to consume from a fully corporatized web. These include many of the people who used to make "websites" instead of "apps" or "platforms". When people complain that it doesn't have as much content as say, Reddit, I look at that as a benefit, it's helping solve the (massive) discovery problem by self-curating thoughtful people who can curate content intelligently and provide real opinions and meaningful thoughts. The signal to noise ratio is much higher, and it's refreshing.

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.

It's possible but not likely or common. Glass is stronger than most people give it credit for. Most "hollywood" glass is actually panes of sugar. You could certainly arrange things so that the gun's pressure wave has a good chance of stressing and breaking glass, but it would take special preparations and effort and the gun would probably have to be very close to the glass. It's almost unheard of for it to happen normally unless you specifically shoot at the glass.

Someone like mythbusters could probably test this pretty effectively, but based on my experience around guns and glass, I suspect they'd come to the same conclusion.

A not directly related but still interesting video was done by the slowmo guys on youtube

Almost like the context matters and the world isn't entirely made up of black and white binary choices because we're not robots or computers and discrete logic does not apply to human moral arguments.

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.

You don't have to be defensive about it, I think it just acknowledges a bit of a public relations tightrope the MIC has to walk. They can't gloat about how we're winning too much (even though they are not just winning, but even doing it with mostly hand-me-downs) or people will start to question whether how much we spend is really necessary. I know why it's necessary, you know why it's necessary, but the average voter doesn't necessarily care.

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

"Number One: In 1945, corporations paid 50% of federal taxes; now they pay about 5%. Number Two: In 1900, 90% of Americans were self employed; now it's about 2%... It's called consolidation; strengthen governments and corporations, weaken individuals. With taxes, this can be done imperceptibly over time." - Leo Gold in "Deus Ex"

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.

If anyone's having problems loading the images due to Google rate limiting, Internet Archive has mirrored the article here

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.

That's kind of like seeing a story where a car crashed into someone's living room and saying "I don't see the benefit of having houses" even though:

• This is very rare
• Not all sites have equal risk of this happening
• The alternatives you would likely propose have even bigger risks.

Yeah it actually makes me feel like there's some astroturf going on. The "reddit defense" backlash seemed to start very suddenly, some while after spez's comments about how the blackout wasn't hurting them got popularized and people started renewing the subreddit blackouts. Almost everyone seemed at least tenatively supportive up to that point, then suddenly these waves of hardcore "reddit did nothing wrong, won't someone PLEASE think of the profits! Everything's fine, just keep posting here, fellow users!" HailCorporate-style comments start pouring into every subreddit and every thread talking about the issue seemingly simultaneously. These is something that seems deeply disingenuous about all of those comments.

Yeah I speculated this was the case when the prevailing opinion of comments on the site made a sudden and drastic change in attitude. IIRC it stated shortly after spez made his infamous comments about how the blackout didn't matter and they didn't see any impact.

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.

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.

The problem is you have no safe way to connect them without building a totally separate electrical system, since they have to be separated from your grid connection. Let me suggest an alternative "alternative energy": LiFePo battery packs/banks are available in a wide variety of sizes, they require no outdoor connections and don't have to be interconnected with each other as they can operate independently and standalone. What you can do is charge them from the grid at low-power-usage times (typically overnight, when the wind farms are spinning, dams are flowing, and nuclear is nuclearing with nobody to use it). Then unplug them during the day and run stuff in your house off battery power, potentially all day long if they're big enough. Technically this is only energy storage, not energy production, but it's an important part of the alternative energy landscape, as energy is very hard to store and renewables like wind and solar depend on the grid's ability to do so, which you will be helping it to do.

They are sometimes sold as battery "generators" for RV/camping as the modestly sized ones can fill a portable role similar to small gasoline generators. Many of them include charging ports for solar too, so you can add solar modules on as well if you want to go that direction, to further increase runtime during the day and provide backup power if you ever need it. They get big and expensive really quickly though, so you can either get lots of small independent ones or a few big ones, but either way you're going to be spending many thousands of dollars.

If we ever end up replacing the supermajority of our power generation with solar, we would need the extra storage at night instead of during the day, but that's likely a long way off and requires a LOT of other load shifting like EVs charging overnight, electric heating at night, etc.

It does not need to go to earth. Take a 1.5v alkaline battery, connect one end of the battery to the other end -- a large amount of current flows, no earth involved. The electric charge that a neuron can produce is basically like tiny cells of a biochemical battery. The problem is unlike a useful battery, the voltage difference between all the individual cells is not (and realistically cannot be) carefully organized in a series or parallel path from positive to negative, instead all the positive and negative connections are jumbled together into a complex network, meaning there's no way of getting billions of volts out of it. It's just not wired that way.

Theoretically if you carefully constructed a series of hundreds of billions of neurons connected end-to-end-to-end in the right pattern you might end up with billions of volts (although end-to-end it would probably be the size of the solar system, so the billions of volts potential wouldn't seem so impressive anymore on an astronomical scale) and you probably can't pack it your neural-battery into a small space without the neuron's insulator (myelin sheath) from breaking down and shorting out that voltage. Also it wouldn't really be a brain anymore at that point. The complex maze of connections are what makes the thinking happen. If you make them all single-connected you've basically just got a really big, low capacity and relatively inefficient battery compared to better chemistries.

Flowing all that current at once will certainly create a lot of heat though, you're right about that. That heat is normally heatsinked by the intracranial fluids and conducted away by the relatively rapid bloodflow through around the brain to be dissipated in the skin and lungs. The brain is basically liquid-cooled and it's a very efficient and tightly regulated system that rarely has issues. Such a high neutral output would probably overwhelm even the relatively robust cooling that bloodflow provides, though, leading to a condition called brain hyperthermia, which is part of the reason drugs like methamphetamine can be dangerous or fatal, as it can result in cell death, and in this case, probably brain death and overall death.

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

Counter rant: This is why we built encryption and VPNs many years ago. This is a solved problem, but rather than solving it you'd rather just complain ineffectually about it. The solution, the product of years of work of technical people and privacy people, is sitting right there staring you in the face available for you to use as a free service, a paid service, or your own self-hosted service. Use a VPN, that's what it's for.

To be fair, in the case of something like a Linux ISO, you are only a tiny fraction of the target or you may not even need to be the target at all to become collateral damage. You only need to be worth $1 to the attacker if there's 99,999 other people downloading it too, or if there's one other guy who is worth $99,999 and you don't need to be worth anything if the guy/organization they're targeting is worth $10 million. Obviously there are other challenges that would be involved in attacking the torrent swarm like the fact that you're not likely to have a sole seeder with corrupted checksums, and a naive implementation will almost certainly end up with a corrupted file instead of a working attack, but to someone with the resources and motivation to plan something like this it could get dangerous pretty quickly.

Supply chain attacks are increasingly becoming a serious risk, and we do need to start looking at upgrading security on things like the checksums we're using to harden them against attackers, who are realizing that this can be a very effective and relatively cheap way to widely distribute malware.

"GL iNet" has a dizzying array of products and some are designed for this (you can find them for sale on the usual scumbags). Surprisingly, for a niche brand you've likely never heard of the firmware is surprisingly robust and has a small but loyal community. Expensive, and you might not want to carry an extra piece of hardware to provide a bulletproof VPN connection, but worth it for the security IMO.

What are your feelings on the Gerald R. Ford? Or does it just fall under the classification of "Nimitz" on your chart as it is continuing in that noble legacy?

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

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.

As usual, Project Farm to the rescue

There's going to be a bunch of caveats here, but basically...

Assuming you're using a NAT router to connect to the internet (basically everyone is nowadays): If you're using a local LAN IP address (10..., 192.168.., or 172.[16-32]..*) then nobody on the internet can access any services on that IP, unless you specifically port forward it through your router. Assuming there's nobody dangerous on your local network (and nobody gets a remote-access virus) and your router itself is not hackable then yes it's entirely safe.

You don't technically need a public domain name to set up an SSL certificate, but to smoothly streamline the process in a way that modern software trusts it, you do. A self-signed certificate can be created for any IP address and it will provide full encryption and avoid interception of traffic between established clients, but you will get a scary warning that the certificate is self-signed every time you connect a new client or browser, because it cannot be verified. It still works though, it's just (intentionally) scary, because it doesn't know what you're doing with it and it doesn't know how to establish trust. You probably don't need this, but it is an option. Setting up a self-signed certificate will have various degrees of complexity in documentation depending on what web server you're using, I would recommend using the simplest guide you can find for the relevant web server if you choose to go that route, you don't need anything complex for this. The keywords you're looking for are "self-signed certificate"

Welcome to self-hosting. Nextcloud is a great thing to self-host, too. Hope you enjoy.

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.

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.

Magsafe is a really great idea, it's just a shame Apple came up with it first and I can't wait for it to be the universal standard for all types of external connectors forevermore. It's as close as we can get to wireless without being wireless.