this post was submitted on 28 Aug 2026
96 points (100.0% liked)

libre

10241 readers
3 users here now

Welcome to libre

A comm dedicated to the fight for free software with an anti-capitalist perspective.

The struggle for libre computing cannot be disentangled from other forms of socialist reform. One must be willing to reject proprietary software as fiercely as they would reject capitalism. Luckily, we are not alone.

libretion

Resources

  1. Free Software, Free Society provides an excellent primer in the origins and theory around free software and the GNU Project, the pioneers of the Free Software Movement.
  2. Switch to GNU/Linux! If you're still using Windows in $CURRENT_YEAR, try a GNU/Linux distribution.

Rules

  1. Be on topic: Posts should be about free software and other hacktivst struggles. Topics about general tech news should be in the technology comm or programming comm. That doesn't mean all posts have to be serious though, memes are welcome!
  2. Avoid using misleading terms/speading misinformation: Here's a great article about what those words are. In short, try to avoid parroting common Techbro lingo and topics.
  3. Avoid being confrontational: People are in different stages of liberating their computing, focus on informing rather than accusing. Debatebro nonsense is not tolerated.
  4. All site-wide rules still apply

Artwork

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] space_comrade@hexbear.net 2 points 1 week ago (1 children)

I guess that sounds reasonable. I just don't see how a strict no AI policy can be reasonably enforced, if somebody is hell bent on shoving AI slop into your codebase they're gonna find a way, it's not like it's particularly hard to make it look like you actually wrote the code instead of the AI.

[–] machinya@hexbear.net 2 points 1 week ago (1 children)

the "cannot be enforced" argument always felt like concern tolling to me. for things like licences, anyone can just copy code from other incompatible projects and claim it's theirs. every policy can be abused and i don't see why this is different.

if someone is hell bent on adding ai code (or any other code, like incompatible licenced code or even backdoors) they will have to make signifficant effort to mask the signals to bypass the review. for everything else it will be a good guideline on how to act when that situation happens instead of depending on the individual maintainers opinion

[–] space_comrade@hexbear.net 2 points 1 week ago* (last edited 1 week ago)

they will have to make signifficant effort to mask the signals to bypass the review.

I guess it depends how significant the effort will be, obviously if somebody just shits out out a 50k line diff with an AI it's gonna be really suspicious right off the bat but a smaller, more contained diff isn't going to immediately raise any flags. Eventually somebody is going to make it really easy to make the AI not sound like an AI at least not as obviously as it does now.

I think eventually maintainers of high profile open source projects are just gonna have to whitelist contributors and just reject contributions from the general public, I wouldn't be surprised if we started seeing interview processes being set up for open source contributions.