• 5 Posts
  • 38 Comments
Joined 1 year ago
cake
Cake day: July 9th, 2023

help-circle












  • This is my biggest challenge with this extension. What’s clickbait to one person is not to another. Several times I’ve come across titles that get mangled when rewritten to lose key points. Or the image gets replaced with a random screen grab. There’s a difference between somebody doing the YouTube face and a title with “the craziest stunt you’ve ever seen” and an artist photo with a title saying the “a crazy stunt jump through a burning hoop”. I’m okay with the latter but dearrow will often remove crazy. The is just an contrived example

    One person could still say “crazy” makes it clickbait, but having some adjectives are fine






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



  • There’s two main ways of doing geo-based load balancing:

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