There was a survey a few years ago that found that some absurdly-large number of Americans think that chocolate milk is produced by brown cows. Like, over 10 million people. I hope it’s not true, but it’s become kind of a meme to convey that Americans are misinformed about a lot of things, and generally just really dumb.

This is madness, but since this is a hobby project and not a production server, there is a way:

• Shrink the filesystems on the existing disks to free up as much space as possible, and shrink their partitions.
• Add a new partition to each of the three disks, and make a RAID5 volume from those partitions.
• Move as many files as possible to the new RAID5 volume to free up space in the old filesystems.
• Shrink the old filesystems/partitions again.
• Expand each RAID component partition one at a time by removing it from the array, resizing it into the empty space, and re-adding it to the array, giving plenty of time for the array to rebuild.
• Move files, shrink the old partitions, and expand the new array partitions as many times as needed until all the files are moved.

This could take several days to accomplish, because of the RAID5 rebuild times. The less free space, the more iterations and the longer it will take.

Isn’t this the doofus who wanted to send a submarine into a cave? Dude doesn’t have the intellectual heft necessary to manage a QuikTrip in Topeka.

But, take this drivel seriously. They like it when rural, red areas report their vote totals first, so that the news outlets will report that Republicans are “leading” early in the evening, before the blue cities finish their counting and overtake the early totals. It’s a cheap trick to sell the claim that the election was stolen to their followers, y’know, the people who think that chocolate milk comes from brown cows.

If you can assign a second IP address to the network interface, then just do so, and bind the docker container to one, and Adguard Home to the other. Otherwise, the reverse proxy based on the server name is the way.

Kind of a self-selecting phenomenon, isn’t it? The haters won’t approach you IRL to berate it, and the admirers aren’t going to seek out an online forum to gush about it.

You win again, gravity!

This is an infuriating aspect of this case. The courts could have held the clinic responsible for this loss without declaring that all frozen embryos are children by invoking the “prime mover” concept. Other courts have used it in, for example, surrogacy cases. In short, that concept holds that it’s the intent of the parent(s) that matters, as the prime movers in the process of bringing a child into the world, not just the mixing of some genetic material. Those destroyed embryos could have become children, as it was the parents’ intention to do so. And if nobody intends to implant embryos, for whatever reason, without the intent to make a child, they’re merely organic material, neatly sidestepping those questions.

But, of course, the court wanted to impose its religious orthodoxy rather than issue a sensible ruling. Now we have those thorny questions.

Now you tell me.

I don’t know about theory, but the big practical advantage to ZigBee is that it works.

Sorry, that’s a shitty thing to say. I’m salty because the only time I tried X10 was 25 years ago, and the experience was less than great. Unreliable switching, spurious commands, slow performance, etc. Sending signals over the power wires sounds great in theory, but in practice there are all sorts of pitfalls, like resistive versus inductive loads, bridging circuits to different legs of two-phase power, or conflicting commands on the wire.

ZigBee has just worked for me, since it avoids all of the potential wiring issues. You just plug a device in, put it in pairing mode, and Home Assistant finds it, interrogates its capabilities, and adds it (by name) with the correct entities. No mucking about with addresses, or adding signal paths to the house wiring. As a mesh network, it’s quite robust, since most plugged-in devices act as repeaters.

The downside of ZigBee, of course, is that it may not work well in WiFi-saturated environments, since it uses the same 2.4GHz frequency band.

I realize that I forgot to answer the question! The wake_on_lan integration has a broadcast_address parameter. It doesn’t explicitly let you pick a network interface, but it might be worth trying to set it to the broadcast address of the Wi-Fi subnet. Then the routing table would ensure that the packet goes out on the correct interface.

For troubleshooting, start at the destination and work back. Run a packet trace on the target machine, and other machines on the WiFi network to see if any WoL packet comes through at all. If not, then look at the VM host.

How does HAOS access the USB network adapter? By pass-thru, so it’s like a USB device connected to the VM, or through a bridge on the VM host? If it’s the latter, a Linux network bridge device is often configured not to pass broadcast packets by the firewall rules. (Things like Docker will enable firewall filtering.) Check that the bridge allows broadcast packets through. If it’s the former, the USB pass-thru, do a packet trace from HAOS to ensure that it’s actually sending the packet, I guess.

According to the ConnectBot issue tracker, it’s not possible to retrieve the private key that it created. You’ll have to make a new key pair, and share the new public key with tildes. The keys are randomly-generated, so the new pair will be different, regardless of whether you use the same password.

Could try the *arr software.

Haha, do you ever feel like the last one to get the joke? I do sometimes.

As one who has studied weather and climate somewhat, this makes total sense. Fucking climate change…

It’s gotten to the point where I kind of hope it’s not the real Margot Robbie. I want to stand in awe of somebody out there who’s this committed to the joke.

The irony of complaining about distracting features that nobody asked for in an article on a site that pops up a video player over the text…

I worked in retail grocery, but I would imagine the situation is the same in other retail outlets. Everybody who has replied so far has a piece of the answer. Sometimes the sale item is a “loss leader,” sold below cost to bring customers to the store, where they’ll buy other products at the same time. Sometimes the price is jacked up before putting it on sale to hide a price increase, or take advantage of the anchoring effect. Sometimes stores take a loss on a product that isn’t selling well, and they just want to get rid of it to free up space. And sometimes the store’s buyers got a really good deal on purchasing inventory, for many possible reasons, like a bulk purchase, supplier clearing the warehouse, or pre-booking the order well in advance. (Manufacturers often give discounts for guaranteed purchases.)

But, yes, as you suspect, sometimes the markup is outrageously high, and they can still make a profit when offering 50% off. (Not often in grocery, which is a low-margin business.)

See the Anchoring Effect.

This is why Robot Santa judged everybody very naughty except for Zoidberg.

Certainly, I just phrased it that way as a lead-in to saying that B5 does definitely get to excitement, and is better for all the buildup. I watched it when it first came out, so at the time we had ST:TNG wrapping up, and only B5 and ST:DS9 as sci-fi on TV. That is to say, we were patient with both shows, because there wasn’t much else (good) to choose from.

Nowadays, there are more sci-fi shows than I can keep track of, so even though B5 is my all-time favorite, I recognize that it may not be as good (too slow?) for first-time viewers as newer shows which benefit from a couple of decades of improvement in TV production.

(The Expanse is definitely in my queue. Just need the time to get to it!)