• 0 Posts
  • 77 Comments
Joined 2 years ago
cake
Cake day: February 1st, 2024

help-circle
  • Oh they absolutely do! My only point is that grid supply must equal grid demand. There are many ways to achieve this, as folks here have pointed out.

    Throttling power generation (turning off/disconnecting PV from grid for example), and storage (chemical, heat, or hydro battery) are all established technologies, they just need to be implemented properly to avoid supply/demand mismatch.


  • If it’s a low resistance path to ground, it’ll get very very toasty! If it’s a lousy ground though, then it won’t…but it also won’t consume any power, so it’s not an effective way of scrubbing off electricity.

    A good ground (low resistance) is found in your household wiring (the ground and/or the neutral). Of you short to that…well…you can guess what will happen! (Let’s hope you have proper circuit breakers.)



  • That is not how it works.

    When you short something to ground, it’s everything in between that needs to dissipate the heat. Think about what “sending it to ground” means—it means you connect the hot to the ground. But with what do you connect the two? A wire? Sure, but you better hope that wire can dissipate all that power, because that’s what it’ll try to do.

    You can’t just “dump power on the ground.” That’s not how it works.


  • This gets posted regularly on Lemmy, and while the economic take is tone-deaf at best, there’s a real issue with generating more power than you can use. You can’t just dump grid power — it needs to go somewhere. The grid needs to consume as much as it generates at all times or else bad things happen.

    There are of course solutions, but that doesn’t mean it’s not an engineering challenge to implement.

    Figuring out what to do with kilowatts is easy, but figuring out what to do with megawatts, at the drop of a hat, is substantially harder.



  • Cool, I recommend it!

    I have my public facing reverse proxy point to my public services, and I also have it set up as a “roadwarrior” VPN to my home. So, I can connect my phone via WireGuard to my VPS, and a local DNS resolves my private services to the private IP addresses in my home network (so, I also run a reverse proxy on my server, for internal services).

    I also have an off-site backup using this — just a raspberry pi and an HDD at family’s, that rsyncs+snapshots over the WireGuard network.

    I’m sure I’m not following all the best practices here, but so far so good.




  • I switched to Technitium and I’ve been pretty happy. Seems very robust, and as a bonus was easy to use it to stop DNS leaks (each upstream has a static route through a different Mullvad VPN, and since they’re queried in parallel, a VPN connection can go down without losing any DNS…maybe this is how pihole would have handled it too though).

    And of course, wildcards supported no problem.





  • I’ve been pleased with it. Family is very relaxed about projects like this, but yeah it’s low power draw. I don’t think I have anything special set up but the right thing to do for power would be to spin down drive when not in use, as power is dominated by the spinning rust.

    Uptime is great. Only hiccups are that it can choke when compiling the ZFS kernel modules, triggered on kernel updates. It’s an rpi 3/1GB RAM (I keep failing at forcing dkms to use only 1 thread, which would probably fix these hiccups 🤷).

    That said, it is managed by me, so sometimes errors go unnoticed. I had recent issues where I missed a week of rsync because I switched from pihole to technitium on my home server and forgot to point the remote rpi there. This would all have been fixed with proper cron email setup…I’m clearly not a professional :)