Seriously. Saying “we’re fucking morons” for being surprised by the 2001 attack on the World Trade Center might be hyperbole, except the same group tried the same thing in 1993! They were just bad at it. Instead of being a KIND OF A REALLY BIG HINT, that incident just kind of disappeared down the memory hole.
Case-sensitive is easier to implement; it’s just a string of bytes. Case-insensitive requires a lot of code to get right, since it has to interpret symbols that make sense to humans. So, something over wondered about:
That’s not hard for ASCII, but what about Unicode? Is the precomposed ç treated the same lexically and by the API as Latin capital letter c + combining cedilla? Does the OS normalize all of one form to the other? Is ß the same as SS? What about alternate glyphs, like half width or full width forms? Is it i18n-sensitive, so that, say, E and É are treated the same in French localization? Are Katakana and Hiragana characters equivalent?
I dunno, as a long-time Unix and Linux user, I haven’t tried these things, but it seems odd to me to build a set of character equivalences into the filesystem code, unless you’re going to do do all of them. (But then, they’re idiosyncratic and may conflict between languages, like how ö is its letter in the Swedish alphabet.)
There was a Republican chode here in Wisconsin who voted twice to prove that people could vote twice. (The clerks caught his double vote, and he got prosecuted.)
Ixonia, Wisconsin solved that problem by just drawing random letters from a hat until they came up with something pronounceable: Ixonia.
But I’m always amused by the street Oxford Place near my house. It’s a street named after a university, named after a city, named after a shallow spot where cattle could cross the river.
Cairo in Illinois, pronounced KAY-row.
He registered as a Republican in 2021, and voted in the 2022 election, so it wasn’t for a strategic vote against Trump, unless he was thinking ahead by several years.
This is madness, but since this is a hobby project and not a production server, there is a way:
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.
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.
Is there any evidence of that? I know that 12% of people who voted for Sanders in the primary ended up voting for Trump in 2016, but where’s the evidence that they were ever Democrats? It’s just as possible that they were Republican-leaning voters who were attracted to Sanders’ message, or trying to sabotage the Democratic primary. That’s a really good narrative for Clinton supporters to soothe their chagrin at the electoral college loss, but as that article points out, that number is actually pretty par for the course in elections.
I feel this in my soul, except about Windows. I’ve got a handful of machines at work that refuse to update to Windows 10 22H2. They give an error code during the compatibility check. Googling that error code returns dozens of forum posts with hundreds of users and “Microsoft support agents” chiming in. They give the same list of suggestions—that don’t work—to fix it. Nobody can say what the error code means, or what the compatibility check checks. The official Microsoft fix is to reinstall.
I don’t want to reinstall. The suite of software these computers run would take several hours to reinstall.
This is typical of my experience with Windows. (I’m a Unix/Linux guy.) I look up how to do something in Windows, and with the official Microsoft documentation, one of three things inevitably happens:
One time, when trying to get Excel to run a mail merge, I ran into all three problems in three attempts.
The same happens with 3rd party sites. They never say the edition of Windows to which their guide refers, and the feature is deprecated or gone. (Most recently it was about getting a Windows 10 start menu behavior back on 11.)
Oh, and since Windows is mainstream, a lot of the information is in the form of AI vomit, and covered in ads and dark patterns.
“Why do you ask? You thinking about banging her?”
You win again, gravity!
The answer is in the headline. WCK is halting its operations. IDF Mission: Accomplished.
If it makes you feel any better, Israel officially hasn’t been a democracy since 2018.
Honestly, I can’t make head or tail of this description. It doesn’t matter where the network devices are physically located; what’s the layer 2 topology?
A lot of other people noticed it and formed OWS and protested until New York City turned off all its cameras and sent the police in to anti-riot them.
Don’t forget the best part: It wasn’t just NYPD. It was a violent crackdown on OWS protests all across the nation, complete with torture and other unconstitutional methods, coordinated in secret by the Obama administration in collusion with the big banks. (For those who have forgotten, integration of government and corporate power is one of the hallmarks of fascism.)
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.
The boat in the old photo (from 1928, apparently) is casting a pretty good wake, and the man aboard is holding a tiller attached to a rudder. It’s impossible to tell for certain with the low-res image, but entirely likely that one of those shapes in the boat ahead of him is an inboard engine.