qx128

Gru

I have not regretted it. Bought a second EV for my family as well. Most of my extended family have also bought EVs and all had positive experiences. I don’t know anyone who has regretted it.

I pronounce it the correct way.

TL:DW…

Money.

In other news, mathematicians have been working hard on calculator detector software. Upon request for comment, leading mathematicians suggested a variety of ideas, such as such as secretly embedding a watermark “58008” (BOOBS) into the decimal parts of pi and e to more easily identify derived calculations. There was consistent sentiment among leading minds that “back in my day we had to work hard to do math, and walk up hill both ways in the snow to school”… and that “there’s nothing wrong with a good ol’ fashion abbicus, dag nabbit!”

Oof. Sadly, events of the last few years support your statement. 🙄

Turns out violent threats are not protected speech under the first amendment. Who knew?!

Fuck around and find out.

I can attest this is true for me. I was shopping for a new clothes washer, and was strongly considering an LG until I saw it had “AI wash”. I can see relevance for AI in some places, but washing clothes is NOT one of them. It gave me the feeling LG clothes washer division is full of shit.

Bought a SpeedQueen instead and been super happy with it. No AI bullshit anywhere in their product info.

It sounds like your issue might be related to how your Docker networks are configured for DNS and internet access. Try these:

1. Check Network Configuration: Ensure your new networks are correctly configured to allow internet access. Docker networks should be able to route traffic to the internet by default unless specified otherwise.

2. DNS Configuration: Since you're using Pi-hole for DNS, make sure the new networks are properly configured to use Pi-hole as their DNS server.

3. Inspect Network Settings: Compare the settings of old_main with the new networks. Use the following command to inspect the network configuration:

   docker network inspect old_main
   docker network inspect cloudflared
   

   Pay attention to the gateway, subnet, and any custom DNS settings.

4. Check Docker Daemon Configuration: Verify that your daemon.json file is correctly set up to use Pi-hole for DNS. It should look something like this:

   {
     "dns": ["<Pi-hole IP>"]
   }
   

5. Verify Container Configuration: Ensure that your containers are correctly configured to use the new network. This can be specified in your docker-compose files like this:

   version: '3.7'
   services:
     cloudflared:
       image: cloudflare/cloudflared
       networks:
         - cloudflared
   
   networks:
     cloudflared:
       external: true
   

6. Check Firewall Rules: Ensure there are no firewall rules on your host or network equipment that might be blocking traffic from the new networks.

7. Test Connectivity: Run a simple connectivity test from within a container on the new network to check internet access:

   docker run --rm -it --network cloudflared alpine ping -c 4 google.com
   

   If this fails, the issue is likely with network configuration rather than the containers themselves.

8. Docker Network Restart: Sometimes, Docker networks need to be restarted to apply changes correctly. Try removing and recreating the problematic networks:

   docker network rm cloudflared
   docker network create cloudflared
   

If none of the above steps resolve the issue, there might be a deeper configuration problem. At this point, it might be helpful to see the exact configuration of your docker-compose files and the output of the network inspection commands.

This guy gets it.

This app got me laid,” says one five-star review on the Apple App Store. “Best way to buy tickets for events. 2nite is the truth and the future,” the horny user wrote.

This author knows what’s up. Most glorious ending to a news article I seen in a while.