Aside from the ethical implications of profiling users or of using a corporatly owned server and model to execute this, I see nothing uniquely concerning about this practice that isnt already a risk of federated social media generally.
Every mod on every instance is free to use whatever tools or standards for moderation they want - that's an intentional byproduct of federation. Similarly, the collection of this data for use with llms is a bygone conclusion at this point - there was never any way of preventing that from happening with a federated network.
I think the only thing here to talk about is the way these questions are being framed as a question of intra-instance policy. We already have communities where moderation abuse can be called out and adjudicated- why pose this as a question of instance administration when there doesnt seem to be any evidence for it?
Right - I cant imagine there are enough rare metals in those components that would make them more valuable as scrap than as working server grade components
Yea, I just think theres a segment of liberals who are in denial about what a "Jewish State" actually is.
Either it's defacto segregation (which happens through social or economic means) and only nominally a Jewish state, or it's state-enforced segregation that requires apartheid and violence to maintain.
Either way - zionism is racist in its most fundamental aspects and should be snuffed out like chattel slavery and South African apartheid
Just so we're all clear - the definition of zionism being used in this context is "someone who supports the existence of Israel as a Jewish state"
I'm thinking that it's quite likely that the .world admin in question would agree with the above sentiment, but would rather not inherit the downstream implications of what it means to define a colonial state by an ethno-religious identity.
Zionists aren't fit to be the local dogcatcher instance admin.
Kinda, but they're specifically saying the the AI agent cannot itself tag the contribution with the sign-off - like, someone using Claude Code to submit PRs on their behalf. The developer must add the tag themselves, indicating that they at least reviewed and submitted it themselves, and it wasn't just an agent going off-prompt or some other shit and submitting it without the developer's knowledge. This is saying 'the dog ate my homework' is not a valid excuse.
The developer can use AI, but they must review the code themselves, and the agent can't "sign-off" on the code for them.
Also - what will holding the submitter responsible even achieve?
What does holding any individual responsible on a development team do? The Linux project is still responsible for anything they put out in the kernel just like any other project, but individual developers can be removed from the contributing team if they break the rules and put it at risk.
The risk of that is relatively low for kernel contributions, though. Most of the work being done is porting existing protocols/firmware into the latest Linux kernel, not creating novel features.
The larger risk is instability caused by bad, hallucinated code because it was submitted under the assumption of human authorship. In both cases, further review by the Linux team can be done if they understand where that code is coming from.
Banning AI does nothing, because theres no way of knowing who uses it without proper disclosure, which wouldnt happen if it were banned. To use an example from the article, it would be like banning code written with the use of a specific brand of keyboard.
Better to have it properly disclosed than to make it illicit
That would be true even if they didn't use AI to reproduce it.
The problem being addressed by the Linux foundation isn't the use of copyrighted work in developer contribution, it's the assumption that the code was authored by them at all just because it's submitted in their name and tagged as verified.
The Linux Kernel is under a copyleft license - it isnt being copyrighted.
But the policy being discussed isn't allowing the use of copyrighted code - they're simply requiring any code submitted by AI be tagged as such so that the human using the agent is ultimately responsible for any infringing code, instead of allowing that code go undisclosed (and even 'certified' by the dev submitting it even if they didnt write or review it themselves)
Submissions are still subject to copyright law - the law just doesnt function the way you or OP are suggesting.
LLMs themselves being products of copyright isnt the legal question at issue, it's the downstream use of that product.
If I use a copyright-infringing work as a part of a new creative work, does that new work infringe copyright by default? Or does the new work need to be judged itself as to the question of infringing a copyrighted work?
And if it is judged as infringing, who is responsible for the damage done? Can I pass the damages back to the original infringing work? Or should I be held responsible for not performing due diligence?
If you think "bad" is too vague, then that isnt a new problem.
Linux has always had to reject 'bad' code submissons - what's new here is that the kernel team isnt willing to prejudice all AI code as "bad", even if that would be easier.
Aside from the ethical implications of profiling users or of using a corporatly owned server and model to execute this, I see nothing uniquely concerning about this practice that isnt already a risk of federated social media generally.
Every mod on every instance is free to use whatever tools or standards for moderation they want - that's an intentional byproduct of federation. Similarly, the collection of this data for use with llms is a bygone conclusion at this point - there was never any way of preventing that from happening with a federated network.
I think the only thing here to talk about is the way these questions are being framed as a question of intra-instance policy. We already have communities where moderation abuse can be called out and adjudicated- why pose this as a question of instance administration when there doesnt seem to be any evidence for it?