@hazel @ncopa It’s not even an RFC. Literally anyone can publish an Internet-Draft. See also: IPv10, IPv4+

@whitequark @artemis for being stuck on qt5 and accepting AI-generated code:

# Andreas Sturmlechner <asturm@gentoo.org> (2026-04-12)
# Perpetually stuck on Qt5 despite recent releases made under the influence of AI.
# A Qt6-based snapshot is provided for testing without keywords, currently as
# app-admin/keepassxc-2.8.0_pre260316-r1, but it is unclear when keywords will
# be restored let alone stabilised.
# Alternatives are app-admin/keepass, app-admin/pass which can import kbdx
# files, app-admin/vaultwarden, app-admin/bitwarden-desktop-bin and probably
# many more.  AppImage or Flatpak versions also available as last resort.
# Bugs #949231, #967905.
# Removal on 2026-05-11.

The China Vehicle Collision Repair Technical and Research Center posted this video of their new battery ejection system for EVs for when they experience thermal runaway, and I cannot stop laughing.

The thought of launching a one-ton battery pack presently ejecting streams of hot flaming gases ten meters away is as horrifying as it is hilarious.

Good luck whoever is to my right!

#cars

Every HackerNews post about IPv6 has some of the worst, most privileged, idiotic, vibe-coded, proprietary, ignorant, 16bit, capital-guzzling, unicorn takes I’ve ever known on the subject:

• IPv6 addresses are too hard to remember.
  So? You’re not meant to remember addresses, that’s why we have DNS, write it down, literally a non-issue.

• IPv6 is confusing and I don’t want to learn something new.
  That’s a personal issue buddy, either start reading or get left behind, that’s what you said about AI right? More things that you depend on this transition.

• NATing has solved the IP limit problem so there’s no point.
  NATing is a plaster slapped onto brain bleed, easy and cheap, but ineffective, it causes a wide range of usability problems, such as blanket IP bans, restrictions on self-hosting, connectivity issue for VPNs both private and corporate.
  To make matters worse, the effects are significantly worse in poorer countries, while Europe, China and the USA have a bounty of IPv4s to use (though China’s still aren’t enough), India has been on critically short supply for a while now with reports of multiple NATed network layers being issued. Imagine if you got banned from Valo because your neighbour 4 districts away got caught cheating.

• We’ve been trying for 40 years and it hasn’t worked so let’s give up.
  OK, we’re going to give up on solving world hunger too then because that’s clearly not getting anywhere, and the energy crisis too while we’re at it, just shut it all down.
  Just because you personally haven’t seen the progress or felt its effects doesn’t mean its not happening, people smarter than you have been working on this before you were born, and at this rate might continue to work on it after you switch careers to Goose Farming.

• IPv6 hasn’t worked so let’s just make IPv7.
  Insane take, despite how it looks, IPv6 support is extremely widespread and ready to go, the reluctance of big tech and ISPs is purely due to the cost implication and lack of enforcement, creating a brand new spec now would enforce another 40 year delay just to assuage your own personal opinion.

• IPv6 is a security risk because the router isn’t NATing.
  Misunderstanding of what NATing does. Even with a public-facing IP on every device, ports are still protected by the router’s firewall.

• IPv6 is a privacy issue because now you can easily identify every device in a home by its public IP.
  A valid concern, if it hadn’t been identified and resolved with the Privacy Extensions to SLAAC that randomises your IP address after a set time period, mitigating the problem to that of your NATed IPv4 Public IP, if not making it more private by muddying the telemetry waters.

#ipv6 #networking

Does Swoosh.Adapters.SMTP (the thing Akkoma uses for sending email) seriously not support IPv6!?

I tried configuring it to use both an IPv6 address and a hostname and domain name resolving only to an IPv6 address and it didn’t work. With an IPv4 address it works fine.

There was a bit more downtime than necessary because I:

• forgot to lower the TTL of the DNS records first
• had to recompile nginx with the http_slice module
• forgot to fix the sequences after replicating the database

The new server will hopefully be faster, it has:

• 32GB DDR4 ECC RAM
• 2x1TB NVMe SSDs in btrfs RAID-1 in LUKS
• i3-9350KF

It also has 8 free SATA ports so if I need more disk space I could potentially get more disks.

Also I’m on PostgreSQL 18 now (rather than 15), which should also be faster.

The database isn’t nodatacow so it’ll get fragmented but that’s probably still better than having it on an HDD and preferable to silent data corruption that randomly appears only some of the time that could occur if I used nodatacow on btrfs RAID-1 (nodatacow also disables checksumming, so if the two copies of the data become desynced btrfs has no way of knowing which one (if any) is correct)