• 34 Posts
  • 469 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle



  • Got it, so just vibes… Well, since you caught me on a Friday with a light schedule…

    Amperage rating is maximum load, not how much it uses the entire cycle. I just so happen to have my washer hooked up to a power meter, and look at that! It doesn’t draw the entire load during the entire cycle (which would look like a flat line)!

    Runtime is not correlated with energy use. Energy is actually much more closely linked to water usage, since it takes a lot of energy to heat up all that water for a cycle, and all that water weight causes extra load on the internal motors. The additional runtime of modern washing equipment is mostly idle time to allow for additional soaking, etc. and not contributing much energy use. Historical trends show a pretty steady decline in energy use. Here’s one study that found a 75+% decrease in energy use per load from the 90’s to the early 2010’s:

    This is interesting, because when partnered with data on tub size, it actually shows that even as loads get larger, energy use has been decreasing over time:

    (source is Association of Home Appliance Manufacturers again).

    Back to your original comments about refrigerators, I’ll just add, going from ~1400 kWh/yr in 1980 to ~400 kWh/yr in 2014 is a 72% decrease in energy use (which is amazing), even while real appliance costs have come down AND volume has gone up.

    IDK where you live, but 1000 kWh/yr for me would cost ~$250 ($0.25/kWh). Swapping a 1980s fridge with a modern one would pay for itself in just 2-3 years. Hell, I could even splurge for a fancy fridge and still have a payback faster than investing in the stock market.

    These gains, largely driven by regulatory efficiency targets, all benefit the consumer and the electricity grid at large. Being cranky about the fact that “they don’t make them like they used to” doesn’t change the fact that meaningful improvements have been made over time.








  • As part of a websites DNS info they have to provide a TTL (time to live). This value can be just about anything but is often in the 30s to 5m range, and serves as an instruction on how long a client should cache the IP address locally before checking for updates.

    This is because IP addresses can change, and you don’t want to experience hours of downtime for all clients every time your IP changes.

    Every time your client queries your tracker for server updates (every few minutes, give or take, based on tracker preferences) it should follow your system DNS settings, which should involve checking your local cache, then going to the upstream server indicated in your system DNS settings.

    If your system is set to a DNS server outside of your local network (e.g., 8.8.8.8) that request should go through your VPN

    If your system is set to use a local DNS server (e.g., 192.168.X.X…), typically either done through something like a pi-hole, or if your router sets itself as the DNS server then forwards all requests, this MIGHT create a DNS leak around your VPN.

    A good VPN like Mullvad should have an option to force their own DNS settings when enabled to prevent this leak.