Younger me: Ooh, I'd better apply this kernel upgrade right away so I'm not vulnerable for very long.

Today me: Will this kernel upgrade be the one with the slop commit that hoses my whole plant?

The problem is those of us who want to build a better world never get the chance because we're always having to defend against those who would see it destroyed before it's ever built.

The headline on the 44Net Connect website is "Next-Generation Digital Amateur Radio Infrastructure". How can it be next generation when it's still using a protocol from 40 years ago and the replacement protocol was first specified 30 years ago?

It's especially mind-boggling for me because I was using 44Net over the air back then. It's how I learned TCP/IP, and in some ways I owe that my career. But how is rehashing all of this an advancement of the state of the art?

#HamRadio #IPv6

This list is getting longer not shorter https://v6check.miyuru.lk/failed #IPv6

As near as I can tell NetBSD is the only OS with its logo in the Unicode standard: 🚩

Headline: We asked AI how it could kill humanity. Here's what it told us.

How the hell is this journalism now? I did not click through. I can't even with this world anymore.

As the Meshtastic/Meshcore war rages on, is anyone working with 802.11ah (HaLow) to build a similar network with more widely accepted standards? Ad-hoc mode + Babel + most of our Internet protocols (XMPP, IRC, SMTP, NNTP) over top sounds pretty fab.

RE: https://sauropods.win/@futurebird/117171017078968423

How about we give the northern states to Canada, the southern states to Mexico, and call it a day?

Want to take a small step toward using #IPv6 but the whole provider landscape looks awful where you are? Start using [::1] instead of 127.0.0.1 when you need to talk to localhost by number. It will do quite a bit toward rooting out some of the last places where there is a legacy dependency, as well as getting you and the people around you used to the new ways.

https://www.congress.gov/bill/119th-congress/house-bill/139

H.R.139 - Sunshine Protection Act of 2025 119th Congress (2025-2026)

This passed the house and is sitting in Senate committee. The President has voiced support for it. It will likely die in committee yet again, but if this somehow passes it will ignore the disastrous failure of the attempt in the 1970s.

Want to become ungovernable? Keep yourself on Standard time anyway. Exercise your freedom to set your clock however you want!

RE: https://aus.social/@Unixbigot/117147733198375419

Very "we don't see any need for #IPv6" energy.

> Please accept cookies to access this content

I cannot fathom any technical reason for this, so how about you eff all the way off.

RE: https://mas.to/@zzt/117130291782813736

some? The number of hallucinations in my critical infrastructure needs to be zero tyvm.

Looks like the solution will end up being to wait for the next #Debian release. From the stunnel changelog:

Version 5.76, 2025.10.18, urgency: MEDIUM
* Bugfixes
* Missing OCSP stapling is no longer logged as an error.

Aug 20 21:20:39 triton stunnel[1535462]: LOG3[0]: OCSP: No OCSP stapling response received

I've tried setting OCSPaia = no and OCSPflag = NOCHECKS in the stunnel config but it still keeps trying. It will never get an answer because Let's Encrypt shut off the responders a year ago: https://letsencrypt.org/2024/12/05/ending-ocsp

Any ideas on how to get it to stop?

I've been delving into the history of the BSDs lately and found a very interesting tidbit. Theo de Raadt, who most people know today from OpenBSD, was one of the founding members of NetBSD. He was asked to resign from that project for behavior that is distressingly common today on LKML: https://mail-index.netbsd.org/netbsd-users/1994/12/23/0000.html

So basically they took "fire brilliant assholes" to heart before it was really a thing. Between this and their swiftness to denounce "AI" (in 2024 when it was still early days of the current hype), they have risen much in my estimation.

#BSD #NetBSD

Said ISP upon being asked when to expect customer #IPv6 availability: "As our current needs are met by IPv4, this is not a priority at the moment."

Wow, I haven't heard that line in 12 years: https://blog.flyingpenguintech.org/2014/03/a-call-to-isps.html

From an ISP this very morning: "We do not have customer #IPv6 available at this time."

It's the "at this time" that really bugs me. It's one of those phrases that people say because it sounds "proper" without thinking about it.

The "IPv6: No Longer Optional" talk was in 2010. RFC 6540 and World IPv6 Launch was in 2012. At _this_ time? What have you been doing with all the intervening time?

General Resolution: LLM usage in Debian
https://www.debian.org/vote/2026/vote_002

Discussion period ended yesterday. Voting starts tomorrow. There are now 8 choices on the ballot. This should be... interesting.

#debian

I was thinking about whether I could go become a bus operator, but I realized today I'd probably get fired pretty quickly for "forgetting" to collect fares.