Got any grapes?

I don't know what building this is, but calling it sky tree just makes me think of these fake cell tower trees.

They could use the heat to keep green houses warm, heat towns, or use it for power generation even.

Which is exactly what I'm suggesting?
I'm not talking about water consumption of evaporative cooling, I'm more talking about the massive power inputs that put 100% of that heat into the surrounding environment. It would be amazing if that could be reduced to only 70% of the energy input.

I've got to wonder if there's some way to install heat exchangers on these data centers to recapture the heat. Nearly 100% of that energy is turned into heat (with a little escaping as sound). I've heard they're wanting to build datacenters inside decommissioned nuclear power plants, so maybe those would even have some of the infrastructure to do it?

It might be tricky if the hot exhaust never gets above water boiling temperature...

Edit: It looks like this is the closest technology we have: https://en.wikipedia.org/wiki/Solar_updraft_tower Building one of those on a datacenter could recover maybe 20-30% of the energy if I'm understanding the article right.

Honestly, I don't know how I feel about solar backfeeding into the grid. There's a lot of safety regulations to get right, and I wonder how it works in a mains power outage? Are all the lines partially electrified with everyone's solar?

What people can do right now, is install solar with a battery, and instead of making the extra energy the power company's problem, you just draw less power from the wall instead.

With a battery alone you can also take advantage of time-of-use billing if you charge it up at night when there's excess grid capacity.

Ah, that's why... I didn't think multiple arguments to operator[] was valid, but my brain is still catching up to C++20 features.

In my configuration I have a server with a public IP that manages incoming connections, and my home network connects to that server via a keepalive connection, so it's actually operating in the same client-server mode you described going through my NAT. This also solves the dynamic IP issues.

When I'm at home, my phone can route directly over my LAN, and when I leave the house it proxies through my public server back to my house (or out to the web depending on what I'm accessing).

Nobody owns it, virus.porn is currently unregistered. $69 is the actual price on Namecheap.

plnkman.com (what you linked, with an L) is also available to buy

p1nkman.com is an actual page registered through Porkbun.com since 2021. Maybe this is P1nkman@lemmy.world's domain, idk.

pinkman.com however is owned by someone through DomainsByProxy.com via GoDaddy. It's been registered since 2004, and is just parked for ad revenue.

This seems like a decent guide on how to set it up:

https://www.cyberciti.biz/faq/how-to-set-up-wireguard-firewall-rules-in-linux/

It's very similar to the config I've got. The nat iptables stuff in step 1 is what enables wireguard to be used as a VPN exit node. (+ net.ipv4.ip_forward=1)

This feels like it has validated my decision to just use plain wireguard and hardcode my client list. It's really not too hard to set up, barely different that configuring authorized_keys or ssh.

It can be yours for only $69/year!

Honestly, the "maintained for one year" part alone would filter out most of the AI slop. The rest of the rules are kind of crazy. I've got several ongoing open source projects, and almost none of them would qualify because I don't spend any time making community posts...