.net core is the future but Mono is still important for running legacy .net framework applications like ones that use WinForms or WPF. That's pretty much it. Anything new should go straight to .net core.
chaospatterns
Looks like Lynnwood and others are capitalizing on this to increase housing around the light rail station:
There's a set of special topics under homeassistant/
that devices also publish to that describe what each topic does and how HA should present it. HA will subscribe to everything under that root topic to discover all your MQTT devices.
Just updated and it looks like this one fixed the log spam:
json_loads was called from hacs, this is a deprecated function which will be removed in HA Core 2025.8.
Use homeassistant.util.json.json_loads instead, please create a bug report at https://github.com/hacs/integration/issues
It's a little weird they don't have a download update button on the new HACS dashboard for an individual repository, now you have to go to Settings > Updates. I also wish I could hide new and available repositories and only show the ones I have installed (you can't seem to select Pending Restart, Pending Update, and Downloaded at the same time.)
As a professional software dev, I worked with pretty much every OS daily. My personal computer was a Windows, my work laptop was a Mac, and I ran my code on Linux so I was familiar with the things I liked and disliked about each. I also ran my own set of server with my websites, mail servers, and various research projects to learn and grow.
Then I decided it was time to order a new laptop and I didn't want to go to Windows 11 because I felt Microsoft was going too much into features I didn't want like Ads, more tracking, pushing AI. Don't get me wrong, I like AI, but it was too much about forcing me to use it to justify their stock valuations.
I also was working on reducing my usage of big tech, setting up self hosted services like pi-hole, Home Assistant, starting to work my own Mint alternative. It just felt natural to get a Framework laptop and try running Linux on it.
I still have a Windows desktop for games and other things, I still use Mac at work. I still like the Mac for it's power efficiency and it doesn't get as hot. Linux has some annoyances here and there, like dbus locking up, or weird GNOME issues, or for a while my screen would artifact until set some kernel params, or the fact that my wifi card would crash and I had to replace it with an Intel card, but I'll stick with it.
As if Sound Transit needs any more reasons to delay and rethink and collect community input on the West Seattle link.
I actually have a double sided male A cable. I was shocked when I got it but I have this laptop cooler that has two A ports on it, presumably to allow a pass through but I'm always nervous that I'll plug it in and fry something.
There's two main ways of doing geo-based load balancing:
- IP Any-casting - In this case, an IP address is "homed" in multiple spots and through the magic of IP routing, it arrives at the nearest location. This is exactly how 1.1.1.1 and 8.8.8.8 work. It works fine for stateless packets like DNS, however it has some risks for stateful traffic like HTTP.
- DNS based load balancing. A server receives a request for "google.com", looks at the IP of the DNS server and/or the EDNS Client IP in the DNS query packet and returns an IP that's near. The problem is that when you're doing Wireguard, it goes phone -> pi-hole (source IP is some internal IP) -> the next hop (e.g. 1.1.1.1 or 8.8.8.8), which sees the packet is coming from your home/pi-hole's public IP. Thus it gets confused and thinks you're in a different location than you really are. Neither of these hops really knows your true location of your phone/mobile device.
Of course, this doesn't matter for companies that only have one data center.
Sorry, what do you mean route it directly? Maybe I didn't clarify well enough.
My DNS is routed over the VPN but Internet traffic is routed directly. The problem is the load balancing is done based on where the DNS server is so say Google even though the traffic egresses directly to the internet bypassing the VPN it still goes to a Google DC near my home. Not all websites do this so its not always an issue.
Yes, but if you hit a company doing DNS based load balancing, DNS is going to return an IP that's near to your DNS server which may not be near your device. That's going to add to the latency.
Ah yeah. Mono didn't support WPF, but Mono did support running WinForms apps natively on Linux without using Wine.