It's like finding out the open source community's got black mold
Uncategorized
52
Posts
18
Posters
3
Views
-
@mcc I didn't even know you could block users on github :O
-
@mcc@mastodon.social uhh are you sure
-
@mcc It's a bit sad to think that warning will remain even if the related code is replaced by humans since history is immutable (unless rewritten but you'd basically never do that on an OSS project)
-
-
@mcc@mastodon.social uhh are you sure
@mcc@mastodon.social oh this is just a github moment. well the one commit is an obviously correct one-line change that was PR'd
-
It's like finding out the open source community's got black mold
@mcc Not to mention people who are very, very excited to huff black mold spores.
-
@mcc@mastodon.social oh this is just a github moment. well the one commit is an obviously correct one-line change that was PR'd
@mcc@mastodon.social i have no idea why the PR author apparently needed claude to change literally a single function call from
panictozfs_panic_recover, but. -
@mcc@mastodon.social uhh are you sure
-
@mcc@mastodon.social oh this is just a github moment. well the one commit is an obviously correct one-line change that was PR'd
I deleted because if there was any chance of error, I didn't want to leave it up, but a PR'd one line change is still enough for me to complain.
The thing is, my understanding is you have to use the tool in a particular way for it to actually create the committed-with header. For more complex uses I believe the header does not show up.
-
I deleted because if there was any chance of error, I didn't want to leave it up, but a PR'd one line change is still enough for me to complain.
The thing is, my understanding is you have to use the tool in a particular way for it to actually create the committed-with header. For more complex uses I believe the header does not show up.
1. It's installed on at least one dev's computer
2. The presence of a header-disclosed commit could imply non-disclosed commits possibly from the same developer
3. The project is not filtering for such code even when it's disclosed
-
It's like finding out the open source community's got black mold
@mcc their vibe-coded slop (zfs) versus my honorable, ornately written tapistry (xfs)
sgi stays winning (i am gonna be shattered if it turns out xfs ALSO uses ai code, my goats had failed me if so) -
@mcc their vibe-coded slop (zfs) versus my honorable, ornately written tapistry (xfs)
sgi stays winning (i am gonna be shattered if it turns out xfs ALSO uses ai code, my goats had failed me if so)@det I'm a bit concerned about RHEL.
-
@mcc@mastodon.social @algernon@come-from.mad-scientist.club (it appears to have been the only commit by that user in 9 years, fwiw)
-
@mcc@mastodon.social @algernon@come-from.mad-scientist.club (it appears to have been the only commit by that user in 9 years, fwiw)
@mcc@mastodon.social @algernon@come-from.mad-scientist.club but also i mean in this case not merging it would be weird, would the alternative be to leave the bug there out of spite?
-
@mcc@mastodon.social @algernon@come-from.mad-scientist.club but also i mean in this case not merging it would be weird, would the alternative be to leave the bug there out of spite?
@leo @algernon If it were my project i would ban the contributor. One line or not they are not following the DCO as written which this project requires. So either the DCO is violated, the DCO has a "you can do anything as long as it's through a hole in a sheet" exception for AI, or the DCO is not enforced at all, or most likely this crept up on OpenZFS and they have never thought about this and did not notice the claude line.
-
@leo @algernon If it were my project i would ban the contributor. One line or not they are not following the DCO as written which this project requires. So either the DCO is violated, the DCO has a "you can do anything as long as it's through a hole in a sheet" exception for AI, or the DCO is not enforced at all, or most likely this crept up on OpenZFS and they have never thought about this and did not notice the claude line.
-
-
It's like finding out the open source community's got black mold
Growing in the cruft.
-
@leo @algernon If it were my project i would ban the contributor. One line or not they are not following the DCO as written which this project requires. So either the DCO is violated, the DCO has a "you can do anything as long as it's through a hole in a sheet" exception for AI, or the DCO is not enforced at all, or most likely this crept up on OpenZFS and they have never thought about this and did not notice the claude line.
@mcc@mastodon.social @algernon@come-from.mad-scientist.club for what it's worth ibm (who is admittedly definitely a biased party here) has espoused the position that the DCO does not ban AI but if you include a Signed-off-by line on an AI-generated commit you are explicitly saying that you take personal liability if a court ends up ruling that AI output infringes copyright
-
@mcc@mastodon.social @algernon@come-from.mad-scientist.club for what it's worth ibm (who is admittedly definitely a biased party here) has espoused the position that the DCO does not ban AI but if you include a Signed-off-by line on an AI-generated commit you are explicitly saying that you take personal liability if a court ends up ruling that AI output infringes copyright
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@k @neil @bert_hubert just to clarify, the AI Contribution Policy applies across any form of contribution to the project and our repositories.
-
Eva Sereny – Romy Schneider, Italy, 1971.
-
@amberage @neil if they'd banned it, you just get people submitting slop without saying it wasn't their own work, and the project would have more risk
-
@xargon @massimolauria Arriveranno. Vedo davvero cose che si muovono.
-
Questa notte all’orecchio m’hai detto due parole
comuni. Due parole stanche
d’essere dette. Parole
così vecchie da essere nuove … https://cctm.website/alfonsina-storni-due-parole/Alfonsina Storni
#alfonsinastorni #poesia #amore #cctmwebsite #anoipiaceleggere #leggere
-
@antoinechambertloir@mathstodon.xyz The distinction you're drawing is a useful one, and I largely agree with it. When translation is imposed on you with no alternative, the responsibility for its faithfulness lies with whoever imposed it.
But it makes me ask: which category does my situation fall into?
I'm writing this reply in English. Not because I chose English as my preferred language of expression, but because if I wrote it in Korean, it would either be ignored or filtered through whatever tool my interlocutor happens to have on hand—and any resulting misreading would be treated as my problem. So I write in English, carefully, to preempt that. Is that a voluntary choice? Formally, yes. Practically, it sits much closer to the “imposed” end of your spectrum than it might appear.
The contract model works cleanly when both parties have genuinely equivalent alternatives. When one party's only real options are “use this tool” or “don’t participate,” the contract framing starts to obscure more than it reveals.
-
Saved recording of Brandon's live feed last night up in Illinois. Starting when large hail and tornado first showed up (about 6:20:00), his window would get smashed shortly after.
https://www.youtube.com/live/NYsANnAhr6k?t=23239
-
Ipocrisia liberal-progressista: quando le bombe tornano “democratiche”
