Why are you hosting a tarball in a git repo? Where is the source for this?
FLOSS virtualization hacker, occasional brewer
Why are you hosting a tarball in a git repo? Where is the source for this?
Slop projects and slop submissions existed before the current crop of AI but it’s certainly lowered the barrier. That said I suspect there are places AI can help. Simple patches, human guided refactores, test cases. We’ll have data points from the projects that turned on the slop cannons and started auto accepting PRs soon enough.


It’s a nod to history and the speaker who had to defy the king.
I’m not sure there is a better way - all the user moderation approaches I’ve seen involve leaning on the regulars to spot stuff. The alternative is dedicated moderators which tends to lead to it’s own problems. I don’t think you want to rely on those who have just signed up as that would be open to abuse pretty quickly.


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.


I do run a bot that can do the initial triage, it doesn’t solve the problem of bugs stacking up in unmaintained areas of the code. I have experimented with auto-fixing the bugs with an LLM but currently the project policy is no AI contributions at all. We are in the process of debating a new policy which might allow for simple fixes to be done with AI.
A super deep dive into working with the x86 memory model in emulation.


Gymnastics might not be a bad alagory for catalysis. It’s all about getting the molecules lined up to make the reactions easier than relying on heat and random collisions to get you there.
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’m sure Reagan deserves a lot of the criticism and he was possibly in early stage Alzheimer’s in his second term. However I mostly remember him being the president in charge when the cold war ended and Eastern Europe was finally liberated.
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.


In the discussions our project are having about how to approach LLM use in the community there has been a lot of consensus in the human taking ownership. Ultimately it’s the human who has to direct the tool and if they have little interest other than blindly hitting accept then we’re not interested in the contribution.


I’d love to know what these techniques are because as far as I can tell it’s just to lie like it’s going out of fashion and insist everything is “fake news”. How do you inoculate against that?


The scary thing is the true believers think it’s all a stitch up. When you hear them talk about how Farage would never do anything wrong they sound just like the MAGA folk in the States.
Nice to see old school demo sensibilities on a “modern” smart watch.
Quite a lot of the trailer was about revamped controls. I might have another go when it drops. I didn’t get far because fighting felt very fiddly.


Some of the AI generated bug reports we get are good because the author had verified them, added a test case and at least reviewed if it is guest trigger able. Yesterday’s flood however was low effort spam.
The project I’m working on has had regular discussion about whether we should move from our email list and patch workflow to a more PR focused approach for a number of years now. Something that works for us greybeards is anathema to younger engineers who grew up on GitHub.
I suspect the current slopocolypse is going to delay that move for a few more years until this wave of disruption has settled down.