Glad to see #Debian come to a reasonable conclusion on LLMs.

> This resolution therefore affirms that generative AI is neither exempt from nor subject to special rules beyond the standards already expected of Debian contributors. The responsibility for every contribution rests with the contributor who submits it, who remains accountable for its technical quality, legal acceptability, and suitability for inclusion in Debian.

https://www.debian.org/vote/2026/vote_002#texte

Glad to see tridge taking the self righteous vitriol hurled his way in the past couple of weeks in good humour. #rsync #LLMs #AI

https://medium.com/@tridge60/rsync-and-outrage-d9849599e5a0

Another #neovim release (v0.12!), another refactoring of my config and extracting part of it out into a plugin. Roadtrain highlights columns over given size.

For a novice, neovim's lua API and plugin writing sure is easier to get a handle on than vimscript!

https://github.com/smlx/roadtrain

One of the operational advantages of ingress over gateway API was the availability of ingress-nginx: a fully-featured, community led, open source controller that was the de-facto standard. By that I mean it was used in tutorials, official docs etc. It was not an "open core" with a paid enterprise tier.

Now that ingress-nginx is being retired, what is the equivalent project for gateway API?

#kubernetes

Had to dip back into the #python world today. Cannot believe that requirements.txt still seems to be state of the art in python dependency management. Happy to be corrected if #pip does actually support cryptographic hashing and verification of dependencies.

hey @spamhaus are your DROP lists supposed to include overlapping netblocks? I just noticed it today when trying to integrate with nftables (which doesn't like overlapping intervals)

Question from a noob with no clue about this stuff:

Is next.js v14 still maintained? From what I can tell there are only two release channels with next.js: Stable and Canary. Right now those correspond to 15.2.x and 15.3.x respectively.

Where does that leave v14 and older versions of next.js in terms of support and patching?

#nextjs #js #javascript

1. There is no single "root cause". IMO this term is harmful because, while it makes for an easily graspable concept, the metaphor encourages identifying a _single_ cause. There is _never_ a single reason behind an incident. Instead there are always several "contributing factors".

I see some common ingrained misunderstandings around "Incident Reviews" / "Post Mortems" in technical orgs.

🧵

I was just linked through to this article by a colleague asking about running services as the "nobody" user on #linux. It is full of very bad, totally wrong advice, but is highly polished and evidently has good enough SEO to be found by people doing #sysadmin that don't know any better.

Given the confidence with which the article is so completely incorrect, I wonder if it is GPT generated. The author page claims not, but who knows? 🤷

https://www.baeldung.com/linux/nobody-user

Anyone else using #neovim with the noctu colorscheme will know it broke with Neovim v0.10.0.

I rewrote it to fix compatibility with Neovim.

https://github.com/smlx/nocte

Listening to the podcast series "Who screwed millenials?" and hearing advertisements for private health insurance, which was on its way to extinction after the introduction of Medicare before being propped up by handouts from John Howard starting right around the turn of the millenium (and successive governments since).

Thanks for the laugh and the screaming-in-your-face irony @guardian

#auspol

h/t to @dcro for the earlier work

Finally got around to writing up how I reverse engineered the encrypted metrics protocol of my solar inverter and smart meter
https://smlx.dev/posts/goodwe-sems-protocol-teardown/

#hack #reverseengineering #solar

Thoroughly bonkers upcoming ASPLOS paper from some UCSD folks: making competitive cloud servers out of old Android phones they bought on eBay. https://dl.acm.org/doi/10.1145/3575693.3575710