Open Innovation Network is a patent pool to protect open source projects from patent trolls. It’s basically mutually assured destruction if the pool has any patents covering products you sell.

DisplayLink have always been touchy about their IP and the lack of open source drivers is the main reason I don’t consider their hardware anymore. I guess they want to stop it getting merged so they don’t end up in a patent battle with OIN.

Why wouldn’t I just run Debian Testing? I’m not sure what this is offering.

Didn’t fish port themselves to rust as well?

It’s not AI usage in the kernel - it’s the increase in AI to do code auditing that had seen the spike in bug reports. A lot of FLOSS projects are seeing this regardless of their use of not of AI to generate code.

I didn’t see anything in particular talking about allowing apps which have used AI although they seem to be using agents to do the repackaging.

According to the site it is repackaging upstream binary releases in a flatpak rather than building anything. I guess for example you could point it at the official Krita app image and make it available that way rather than relying on the community flathub build.

Slop has existed before AI but it has lowered the barrier to generating it. Having no AI policies isn’t really working because the slop posters don’t declare it and as a reviewer you don’t want to be second guessing a potential contributor.

We are probably going to move to a policy that allows narrow use of AI tools but emphasises human understanding and ownership as mandatory components of contribution.

Other firmwares exist, even libreboot is a fork of coreboot. The availability of the code is not an automatic invite to start judging it’s authors. The four freedoms are there so exercise them.

Good luck getting the masses to adopt them. Passkeys seem like an improvement on trying to get your average meat brain to remember several unique passwords.

I can absolutely understand some of the objections and I understand why writers and artists are pissed. My code has always been free software so I don’t object to it being in the training sets because that seems fair use according to the four freedoms.

The power usage is definitely a concern but that holds up for all computing. I don’t see people up in arms about inefficient CI loops retesting the whole world for a single line change. Think of savings that could be made!

The phrase vibecode has become totally meaningless. The original use was too “give in too the vibes” and let the agent go wild. There is no indication that is what Linus is doing.

The fact is LLM’s have proven to be good at finding bugs. Suitably constrained they can be diligent and helpful assistants.

The Bun experience is instructive and if that was Linus’ end goal it would be concerning but I don’t see any evidence that any of the Linux maintainers are interested in that sort of wholesale conversion. The good projects with taste will adjust to the new tools and the slop projects will eventually collapse under their own contradictory architectures.

The reactions to this have been pretty hysterical considering this is an experimental branch on his own repository. I’m not surprised he might experiment with using AI agents to solve a particular pain point to see how it does. This is using agents to experiment with things that you might not have time to address normally.

Another recent example is the build system where the author said:

An LLM was used to first determine where the bottlenecks were then to figure out how to improve them. It generated a lot of code, much of it hideous.

I extensively audited and rewrote a lot of it, and heavily edited commit messages, the cover letter and comments.

off-loading the boring grunt work of identifying bottle necks and trying new approaches seems like an ideal task for a junior agent to deal with as long is you don’t YOLO the result to the lists for other humans to de-slopify for you.

I do like Jeff’s videos, he comes across as a true engineering nerd. I find his SBC reviews to be pretty thorough and some of his other videos make for an interesting side quest on stuff he’s interested in.

I certainly don’t view DeVaults purity list as the authority on if I should watch someone’s videos or not.

Why are you hosting a tarball in a git repo? Where is the source for this?

If the bugs were being found in code that is used heavily in production I’d agree. Spamming the tracker with 100’s of bugs in random unmaintained areas of the code base just wastes everyone’s time. Perhaps as a project we should be more aggressive in deprecating code but the threat profile for someone running firmware blobs from their camera is very different from people launching untrusted guests on their shared hosting infrastructure.

Yes, I misspelt it in my comment. It’s currently working well but I worry that the main developer will burn out. They usually have to add new thunks every new Minecraft release.

Pretty much cross play with tablets and the PlayStation.

I wonder if lepton will solve the Minecraft problem. Waydroid was broken by some recent drm changes which are unlikely to be reverted although mcplauncher still seems to work although it’s been awhile since I tested on my SteamDeck.

I think it’s a mistake to think of it as a homogeneous community. The original free software hackers where a mix of libertarians working alongside communists. The growth of the distros brought there own communitarian vibes. And that’s fine, the license is the thing that allows everyone to potentially benefit whatever direction any particular group go in. Don’t like the direction don’t follow that group.