Death by a Thousand Slops
daniel.haxx.se
Death by a Thousand Slops
1–10 of 149 posts
Re: Death by a Thousand Slops
#2I think eventually all OSS projects/repos will suffer with this.
My bet is that git hosting providers like GitHub etc. should start providing features to allow us for better signal/noise ratio
Re: Death by a Thousand Slops
#3I think eventually all OSS projects/repos will suffer with this. My bet is that git hosting providers like GitHub etc. should start providing features to allow us for better signal/noise ratio
Githubs owner is betting the farm on pushing slop, so that seems unlikely to happen there anytime soon.
Re: Death by a Thousand Slops
#4I think eventually all OSS projects/repos will suffer with this. My bet is that git hosting providers like GitHub etc. should start providing features to allow us for better signal/noise ratio
Why would GitHub develop features that are adversarial to one of Microsoft’s favorite products?
Re: Death by a Thousand Slops
#5For all the discussions about the slopification of the internet, the human toll on open source maintainers isn’t really talked about. It's one thing to get flooded with bad reports; it's another to have to mentally filter AI-generated submissions designed to "sound correct" but offer no real value. Totally agree with the author mentioning the emotional toll it takes to deal with these mind-numbing stupidities.
Re: Death by a Thousand Slops
#6Oh god, going through some of the reports listed on the bottom of the page feels like a nightmare. I cannot imagine how it is for the actual maintainers.
I wonder what's the solution here. You need to be able to receive reports from anyone, so a reputation based system is not applicable. It also seems like we cannot detect whether a piece of text was generated with LLM..
Re: Death by a Thousand Slops
#7I think eventually all OSS projects/repos will suffer with this. My bet is that git hosting providers like GitHub etc. should start providing features to allow us for better signal/noise ratio
Why would GitHub develop features that are adversarial to one of Microsoft’s favorite products?
E.g. to secure the quality of training data?
Re: Death by a Thousand Slops
#8Reading this particular instance of slop was especially galling. It's like the world's slowest ChatGPT dialogue via a bug tracker.
Re: Death by a Thousand Slops
#9I think eventually all OSS projects/repos will suffer with this. My bet is that git hosting providers like GitHub etc. should start providing features to allow us for better signal/noise ratio
Depends. I'm not suffering it at all, but I'm a sort of research project producing variations on audio processing under MIT license.
And I don't take pull requests: only exception has been to accomodate a downstream user who was running a script to incorporate the code, and that was so out of my usual experience that it took way to long to register it was a legitimate pull request.
Re: Death by a Thousand Slops
#10> Maybe we need to drop the monetary reward?
That would likely fix some of it, but I suspect that you'd still get a lot, anyway, because people program their crawlers to hit everything, regardless of their relevance. Doesn't cost anything more, so why not? Every little hit adds to the coffers.