• 1 Post
  • 13 Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle




  • I do have static IP and no ports blocked, so that’s no trouble.

    I am looking for something low maintenance though, something I don’t need to constantly pester beyond updates.

    Containers are preferred, as I already run a pretty complex Docker stack.

    But you seem to have completely missed the last paragraphs of my post.






  • Just because it’s open source it doesn’t mean there’s not a person or group of people deciding what happens to the ‘main’/‘upstream’ version of it.

    Sure you can fork it, and remove all AI contributions, but who will use your fork?

    When people say “the Linux kernel”, they mean the version maintained by Linus Torvalds. They might mean a fork for a specific SoC or manufacturer or distro, but those are all just the Linux Kernel maintained by Linus Torvalds plus a few patch sets. There’s no considerable divergence.

    Linus’ stance was initially “no AI written code”. And he does have final say in what goes into the repo he maintains. Now he’s changed that tune, he allows AI written code, and no matter how many forks you make to strip it out… what matters is Linus’ upstream.




  • Open source maintainers have enough trouble without trying to ban all AI generated code just to comply with a distributor.

    AI code is inevitable. Even if you outright ban it, people will try to sneak it in. Lets say the change is literally just changing the order of calls to fix a bug - but the person who found and fixed the bug used AI to do so. Do you ban that? If it’s not disclosed, how would you know? After all the commit is literally just a line order swap. What if the committer actually hand wrote that fix but used AI for the PR body because they don’t speak English well and don’t want to appear dumb?

    The best practice is to allow AI-generated code as long as the person providing the commit can properly reason about its function - meaning they understand what the code does and have done their due diligence. Good quality AI generated code isn’t the issue, it’s the skiddies who think prompting Claude with the most basic queries and blindly accepting the output until the one thing they wanted to achieve works, results in usable code. It results in unmaintainable slop. You need an actual engineer with experience to review it, but maintainers don’t have that capacity, so banning slop and requiring contributors to understand what they’re trying to get merged is the best way forward.