Egregoros

@SprocketClown

The way I read it in this context is that an existing codebase has license (whether GPL, LGPL, or proprietary or whatever), and that by "laundering" the codebase through an LLM, the output no longer retains the retains the license terms. In the US at least, the Supreme Court has ruled that LLM output is uncopyrightable.

So as @cwebber highlights, either the licensewashing works, in which case LLMs can scrub licenses off proprietary codebases giving a leg up on "reproducing" proprietary codebases into the public domain; or it doesn't work, in which case LLM-produced code becomes subject to the licensing of the original code.

@lanodan

Annoying though when the big senders re-send from different addresses.

10.0.0.1: Hi, I've got some mail for you
My gray-trapping server: um, try again in a few minutes (notes 10.0.0.1 as the sender)
10.0.0.2: Hey, here's that message I tried to deliver to you earlier
MGTS: Um, I have no record of you trying to send so try again in a few minutes (notes 10.0.0.2 as the sender)
10.0.0.3: Hey, here's that message I've tried twice to deliver to you
MGTS: Um, I have no record of you trying to send so try again in a few minutes (notes 10.0.0.3 as the sender)
⋮

[sigh, glaring particularly at Outlook.com, I recall @pitrh blogged about this annoyance a while back but I can't disinter his post to link to]

@mia @aetios

@mirabilos

Yeah, I'm sure there are ways to cobble together such a solution on Linux, but ZFS (optionally with GELI) makes it so brain-dead simple. No need to learn dm-integrity commands to control the integrity bits, luks (or any of a dozen other encrypted-device iterations) for encryption bits, pv* commands to control the physical volumes, vg* commands to control the volume-groups, lv* commands to manage the logical volumes, then manage file-systems atop that, and then try to tune the right blocksizes for optimal reads/writes. Just zpool(8) and zfs(8) for the whole thing.

I played that Linux game once and that was more than enough 😆

@rl_dane