Never seen it. Something about French ladies and floating door space?

How so?

I’m going to take a swing at the moon reflects a relatively uniform spectrum of light from the sun but our varied atmospheric conditions can alter the refraction of that light.

If it’s mentioned up front and fixed then it’s fine. One way or another the restaurant needs to cover it’s costs and it’s either done via inflating the price of the food or a fixed service fee.

What I hate is a discretionary tip suggestion because suddenly I’m made to be responsible for how much the staff get.

The most useful use case for me is querying a knowledge base in NotebookLM. I work on CPU emulation and it does a very good job of extracting the relevant information from thousands of pages of dry technical specs and preparing the requirements for implementing a particular feature.

The Deep Research mode of Gemini is pretty good at generating some briefing notes (with links) and can do that in the background once you kick it off.

On the potentially bright side maybe this will make people think harder about which model to use for which task. You don’t need to feed your entire code base into Opus when a Gemini Flash sub-agent can do a perfectly fine job running grep and compiling a summary for the main agent.

After the sequel it’s usually diminishing returns for the plot.

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.

Was he inverted?

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.

Funny 😂

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.