They should make a separate mailing list specifically for people who use AI, to concatenate their results and boil it down to something manageable for a human to review.
It’s like having a porch light a few feet away from the door to attract all the moths so they don’t come inside whenever you open the door.
Why do you think the kind of obnoxious cunt who uses an LLM to spam a Linux mailing list would voluntarily use another? AI-bros, as a rule, do not respect others.
While this kind of staking could deter bad actors, it might also deter casual contributors. If I just so happen to stumble upon a kernel bug and have a quick and easy way to report it, I’ll probably do so. If you make me jump through a lot of hoops to first make a deposit, I might not.
Maybe force it some way, I don’t know. Find a backend software solution. Figure a way to programmatically identify when AI was used and automatically route it somewhere else? Or force them to fill out a dropdown menu saying whether AI was used or not?
You’re telling me the Linux Foundation can’t engineer a viable software solution?
If it were that easy, we wouldn’t be in this situation. Education wouldn’t be under attack, social media wouldn’t be flooded with bots. LLM detection is incredibly unreliable and anyone saying they’ve cracked it is selling snake oil. There are techniques for image diffusion that are holding up currently but text is another story.
Checking a checkbox again relies on these chucklefucks being honest and decent and respectful people which they fundamentally aren’t.
It could be as simple as creating a whitelist of verified contributors who are trusted and routing everyone else through a filter. Or identifying the most serious offenders by looking at volume and frequency of contributions, making a list of the ones that are obviously automating, and routing those through the filter, which should still significantly reduce the number that require human review.
Neither of which are perfect solutions, but it could make the situation more manageable if you don’t trust people to be honest about whether their info was generated with AI.
More like use a deterministic program to concatenate all the deltas, merge redundant ones, and present any conflicts to a human to rectify. Then a human can give it a final review before finalizing anything.
They should make a separate mailing list specifically for people who use AI, to concatenate their results and boil it down to something manageable for a human to review.
It’s easy, we create a problem with AI, and the best solution is to use even more AI, and when everyone is dependant on it to manage digital infrastructure that used to function for decades, then we raise the price.
They should make a separate mailing list specifically for people who use AI, to concatenate their results and boil it down to something manageable for a human to review.
It’s like having a porch light a few feet away from the door to attract all the moths so they don’t come inside whenever you open the door.
Why do you think the kind of obnoxious cunt who uses an LLM to spam a Linux mailing list would voluntarily use another? AI-bros, as a rule, do not respect others.
Maybe use idea from PGP/GPG which is web of trust where people are added based on others vouching for them.
To make it somewhat available others can join as well but for a fee and at the lowest level. The fee would be determined on amount of cunts.
If somebody would not follow rules they would be marked as not trusted but money wouldn’t be refunded they would have to pay again.
The money could be used as donations to fund the project.
If there’s somebody who couldn’t afford those fees, they could still find someone who could vouch for them and bypass it.
While this kind of staking could deter bad actors, it might also deter casual contributors. If I just so happen to stumble upon a kernel bug and have a quick and easy way to report it, I’ll probably do so. If you make me jump through a lot of hoops to first make a deposit, I might not.
Maybe force it some way, I don’t know. Find a backend software solution. Figure a way to programmatically identify when AI was used and automatically route it somewhere else? Or force them to fill out a dropdown menu saying whether AI was used or not?
You’re telling me the Linux Foundation can’t engineer a viable software solution?
If it were that easy, we wouldn’t be in this situation. Education wouldn’t be under attack, social media wouldn’t be flooded with bots. LLM detection is incredibly unreliable and anyone saying they’ve cracked it is selling snake oil. There are techniques for image diffusion that are holding up currently but text is another story.
Checking a checkbox again relies on these chucklefucks being honest and decent and respectful people which they fundamentally aren’t.
It could be as simple as creating a whitelist of verified contributors who are trusted and routing everyone else through a filter. Or identifying the most serious offenders by looking at volume and frequency of contributions, making a list of the ones that are obviously automating, and routing those through the filter, which should still significantly reduce the number that require human review.
Neither of which are perfect solutions, but it could make the situation more manageable if you don’t trust people to be honest about whether their info was generated with AI.
Maybe they could use an LLM to make a summary of the results!
Ideally, If the AI was truly any good at finding the bugs, a well trained AI could give it the ole wheat and chaff action.
we’re not there yet.
More like use a deterministic program to concatenate all the deltas, merge redundant ones, and present any conflicts to a human to rectify. Then a human can give it a final review before finalizing anything.
I get it - like an AI summary!
It’s easy, we create a problem with AI, and the best solution is to use even more AI, and when everyone is dependant on it to manage digital infrastructure that used to function for decades, then we raise the price.