• 8 Posts
  • 38 Comments
Joined 5 months ago
cake
Cake day: February 3rd, 2026

help-circle

  • That is very anecdotal, and unlikely to apply to anyone else. If you charge 30-90% in an hour, that means that you must have found a cheap super charger? Not even just the regular 22kW fast chargers? Where I live all the super chargers is quite expensive, like 1.5x the price of gas /km. Which is fine as you would mainly use them fore rare long trips. Meanwhile charging at home is like 1/4th the cost of gas /km, and regular public 22kW chargers about the same as gas.

    Having to regularly wait 30 minutes somewhere to charge can definitely be a real inconvenience, but I buy that it’s nice to just sit and relax for a bit though.

    Also, isn’t regular super charging very bad for the battery health in the long run?









  • Important context to the headline:

    Temperatures downwind of data centers averaged 1.3 to 1.6 degrees F warmer than upwind temperatures and reached as high as 4 degrees F above upwind temperatures. The heat impact was detectable up to a third of a mile, or about five city blocks, distant from the perimeter of datacenters.

    So it sounds like a very local effect, that is not measurable more than 1/3 miles from the datacenter. Doubt it will be noticeable at all in a climate as warm as Arizona



  • In the home/lab, I use public addresses with mostly SLAAC, but the host server has a static IP. I get A public /56 prefix via DHCPv6-PD from my ISP. There is a bit of a pain point if the prefix changes but it hasn’t happened since I moved here.

    My ”production” setup is a bit more controversial. Since Hetzner charges extra for extra IPv6 subnets I simply created small /80 subnets for the VMs. While this does mean that SLAAC doesn’t work I can simply generate and assign static IPv6 IPs, same way as I do with IPv4. All generated from an ansible playbook that creates the VMs.

    I have some ULA ranges as well, but it’s a bit of a special case as I only use it as internal IP ranges in a Kubernetes cluster. This is completely separated from the external network, with the cluster doing NAT to the node IPs anyway (even for IPv6), and all internal traffic being on an overlay network.



  • I’ve set up a https://stalw.art/ server recently, and I’m quite impressed. I appreciate that the entire mail service stack is taken care of by a single unified service, except webmail but Bulwark seems really solid. It also works nicely together with Postgres and S3, so I can have the same backup strategy as most other apps I’m hosting.

    First and foremost for the outgoing needs of https://nord.pub/, but I’m seriously considering moving personal domains to it as well.

    For infrastructure I’m using dedicated Hetzner hosts, with extra IPs for the mail servers, so that reverse DNS is consistent.

    Largest problem I’ve seen is that Outlook.com is classifying the emails as spam, even with SOF, DKIM, DMARC properly set up… which is a big reason I’m hesitant to move all personal email as well. I realised that it could be a problem if I ever want to contact companies who use Office 365, which is a lot.



  • Best option is probably to look for providers that support custom domains, so you can point your domain directly to their mail servers. This usually require a paid subscription. Upside is that you retain control over your domain without having to host any email server.

    The problem is that by putting a mail relay in between, while technically possible will break the SPF and DKIM chain for all emails that you forward. I don’t think there is a good way around this since they check against the senders domain (and assuming that you can’t get the email provider to trust your relay server)








  • I’ve been running straight Ubuntu with ZFS-on-Linux since 18.04, and it has been smooth sailing. If you’re running a lot of containerized things it’s very convenient to just be able to bind mount ZFS dataset into containers.

    Normally I prefer CentOS/RockyLinux, or some other EL distribution, but in this case I really appreciate that Canonical isn’t purist enough to ship ZFS as a loadable kernel module that is guaranteed to be in sync with the shipped kernel. And don’t have to deal with DKMS.