FLOSS virtualization hacker, occasional brewer
There were some posts yesterday with chunks of the various depositions talking about the employee hand book explicitly encouraging a boys will be boys culture.
ETA: Found it https://bsky.app/profile/joshuaerlich.bsky.social/post/3mk5w4sdpq22a
Even Debian has popcon as an opt in. I can see why collecting data about hardware and package choices is useful to Ubuntu. I didn’t think they collected any personally identifying information.
I also have a diverter which heats up my hot water tank which saves on gas, especially in the summer.
It will be fun watching those users who first make the jump to the new project.
Export to the grid, for every kWh I export during the day I can afford two kWh overnight.
If it’s finding valid vulnerabilities then it’s just another tool like static analysis, fuzzers and sanitizers. There definitely seems to be a difference in quality compared to earlier generations that were behind the sloppy avalanch of reports.
I think the article is over complicating things. I work in a project which is heavily forked for a variety of reasons. While it’s academically interesting to look at the reasons for those downstream forks we have no interest in going to the considerable effort of tracking them all.
If you can take a project and use an LLM to enable your niche use case then more power to you. FLOSS was never about ensuring all patches flow upstream.
They don’t have to be. They know what they asked the LLM to do. They know how much they adapted the output. You usually have to work to get the models to spit out significant chunks of memorised text.
No, that’s why the author asserts that with their signed-of-by. It’s what I do if I use any LLM content as the basis of my patches.
If the 2-10% is just boilerplate syscall number defines or trivial MIN/MAX macros then it’s just the common way to do things.
If you are using MakeMKV when ripping you can override the filename template. So I name them for example “Show s01e04+” based on the disc I’m ripping. Then once encoded it’s relatively quick to rename the files with the full episode number. I personally use dired in Emacs because a macro makes short work of the renaming but I’m sure other solutions are possible.
My Bravia experience improved markedly when I replaced Sony’s default home screen with the Projecivity Launcher.
My kids are growing up in this environment and they already have an eye for ai slop. I suspect it’s the same thing that led to OpenAI’s TikSlop “product” is getting canned. After society had gotten over the sugar rush excitement of new and shiny toys I suspect the interest will fade and people will crave the connection you get from real art made by real people.
At least I hope that is what will happen. We might have to do something to hold the tech companies accountable for their dopamine trigger machines though.
Where are you seeing the 2-10% figure?
In my experience code generation is most affected by the local context (i.e. the codebase you are working on). On top of that a lot of code is purely mechanical - code generally has to have a degree of novelty to be protected by copyright.
I was glad to see Niko publish his initial work and look forward to seeing how it’s gone.
They don’t, just like they don’t with human submitted stuff. The point of the Signed-off-by is the author attests they have the rights to submit the code.
Isn’t that like the extract opposite of what everyone wants which is free flowing shipping?
After the sequel it’s usually diminishing returns for the plot.