It is the interpretation of the Judicial Branch of the United States government and the United States Copyright Office, the best authority on copyright law in the United States.

But yes, much like every single other law in existence, it’s not universal. (I mean, unless we’re also talking about the laws of physics.)

And yes, if the AI generated code is a copy of copyrighted code, then it would still be copyrighted, but that’s an even worse problem for Codeberg than it being public domain.

It is.

https://sciactive.com/human-contribution-policy/#More-Information

In the Office’s view, it is well-established that copyright can protect only material that is the product of human creativity. Most fundamentally, the term “author,” which is used in both the Constitution and the Copyright Act, excludes non-humans.

– II. The Human Authorship Requirement

If a work’s traditional elements of authorship were produced by a machine, the work lacks human authorship and the Office will not register it. For example, when an AI technology receives solely a prompt from a human and produces complex written, visual, or musical works in response, the “traditional elements of authorship” are determined and executed by the technology—not the human user. Based on the Office’s understanding of the generative AI technologies currently available, users do not exercise ultimate creative control over how such systems interpret prompts and generate material.

– III. The Office’s Application of the Human Authorship Requirement

Some technologies allow users to provide iterative “feedback” by providing additional prompts to the machine. For example, the user may instruct the AI to revise the generated text to mention a topic or emphasize a particular point. While such instructions may give a user greater influence over the output, the AI technology is what determines how to implement those additional instructions.

– Footnote 30

(All from this document from the US Copyright Office: https://www.copyright.gov/ai/ai_policy_guidance.pdf)

Considering AI generated code is public domain, so not exactly open source licensed, this is a good move.

Fediverse:

If it’s orbiting a star, it’s a planet. If it’s orbiting a planet, it’s a moon. If it’s orbiting nothing, it’s a target.

(This thing is a planet. It orbits a star. Doesn’t matter if that star orbits another star. By definition, it’s a planet.)

Love it.

Real men need testosterone supplementation?

Ok, cool, so we agree that trans men are real men.

Official response from the United States Federal Government:

“Snitches get stitches.”

Is there anyone that actually wants this garbage?

I would’ve guessed in a million years.

I work at a scuba shop. This would be an equally dumb question there.

279 miles to E and E gives you boobs. Is that what this means?

I’m talking about when you update the system. Unless you reboot to do the update, the system can be using outdated binaries until you reboot. Apt will tell you about them, but I don’t know about other package managers.

This is the best solution.

Yeah, a file system snapshot is another way of achieving safe upgrades. There are upsides and downsides of all approaches though.

Rolling back to a btrfs snapshot might be harder than just picking the other ostree image in GRUB. And you still have the problem where old binaries might be running when only the new binaries/libraries exist on disk. But it also saves space on disk compared to an immutable distro, and it’s much easier to make changes to system files. Every approach is a compromise.

It’s cause of the way an immutable system works. In an immutable system, the entire system is an image. Two are stored on disk. One is active, and the other is usually the previous image. When you update, it overwrites the old image. The current image stays untouched. It’s only once the new image is completely written to disk that it’s marked as the current image.

Package managers are working on the currently running system. They write over the only set of system files, and they can only do that one file at a time, so you can rely on the file system’s journal to make sure each file is correctly written, but there’s nothing preventing the system from being only half updated. If a package relies on a package that hasn’t been installed yet, and the update fails before it gets installed, that package is broken.

In a system like Ubuntu or Fedora, that’s mostly ok, because packages are always built for the kernel and library versions available throughout the lifecycle of the release. So a half updated system is probably fine and will continue the update when rebooted. But for rolling releases like Arch, or for a release upgrade like Ubuntu 25.10 to Ubuntu 26.04, a failed update might mean a broken system.

The copilot butthole has easy access safety flaps.

Fresh grime! Get your fresh grime here!

Your latest meal gave you explosive diarrhea.

All of my meals give me explosive diarrhea.

We are not the same.

Run an update on a traditional system, and pull the power plug out when it’s half way through. If it recovers when you reboot it, you got pretty lucky.

Now do the same with an immutable system like Bazzite. It will be running the pre-update image when you reboot it. No harm done. It’s essentially impossible for an update (or even a failed update) to brick the system. You can always roll back to the last working image.