Alex

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

I did 4 charges on my 480 mile journey to Scotland which took 30-45 mins each. I didn’t mind too much because it’s a long drive and I had to eat but a bit snapier would have been nice for two of the stops.

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 wouldn’t say it’s totally legacy. (v)ram bandwidth does matter and while the Apple M-series chips do well with their unified memory architecture don’t forget it’s fixed because it’s part of the CPU chip.

I don’t doubt that locally hostable models will be important for agentic tasks but I suspect they are still going to be bigger than most can comfortably host for time being. I still think there will be a place for the super large models for more complex reasoning although how much will be due to the intrinsic knowledge in the weights and how much due to the plumbing around them remains too be seen.

And if course LLM’s are not going to be the end point of the search for AGI. Whatever their architecture they will still need copious amounts of compute.

On the other hand it’s legitimately one of the wonders of the digital world. A communally edited source of knowledge free for all to access. While it’s good to scrutinise foundations and how they are run I’ve not seen anyone propose a better solution so far. The data is freely licensed so forking is possible but it’s not really the technical details that make Wikipedia the resource it is today.

I thought Episode IV was in the initial crawl text.

ETA I’ve just checked and apparently it was added in the special editions, the original 1977 crawl just started with the story.

Is this a sign of Lemmy’s popularity that we are now getting thirst spam?

Because running servers costs money. The project I work on gets donations towards it’s CI costs and it’s not insignificant.

Your making a big assumption extrapolating from one particular study involving Java code and a static analyser.

How is that patch sloppy?

I feel the term slop is being overused to cover anything an LLM has touched. If I ask an agent to re-read a mail thread for me and apply the changes to my tree to review is that slop? Would you feel better about it if I copy and paste from email to code in my editor?

I’ve just been doing a bunch of bug triage which was mostly driven by the agent although I checked the issues where it had commented. Was that slop? Ironically a lot of the issues where AI generated although for the most part more complete than a lot of the purely human submissions we get. Are those bug reports slop? What about the poorly drafted human ones?

That’s not kernel policy but LF guidance. From the kernel’s point of view patches still have a high bar to pass to get merged and I don’t think we have enough data yet to see if LLM based submissions to the kernel have a higher or lower error rate than humans.

I certainly feel the uptick in LLM reports though - one of the projects I’m working on is seeing a deluge of them at the moment.

What’s wrong with backports and at a push snap/flatpak/appimg for apps? One of the main reasons I’m on Debian stable is I don’t want the underlying plumbing of my system changing radically.

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.

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.

So algorithms then?

LLMs have some interesting properties and certainly can do a good job sifting through large amounts of raw data. They are however a very brute force approach compared to say a network routing protocol. Sooner or later people will start to realise (again) that engineering is about trade offs and you need to work out what your constraints are and stop trying to solve every problem with massive amounts of multiplication.

I swear people have rose tinted glasses as to the state of the init system before the current generation of system management daemons.

If you really want to have Debian without systemd there is always Duvean but the Debian architects are free to choose the technologies that solve the very real system orchestration problems that exist.

Who are the community employing? Why do they need consulting before code changes are made?