Skip Navigation

Posts
44
Comments
1084
Joined
4 yr. ago

  • If the hard legal reality of all LLM generated code having a high risk of breaking copyright is "feelings" for you, then sure 🙄

  • It's not prejudice if it is objectively true 🤷

  • Most LLM users don't try to hide it and the commit pattern is a result of the LLM assisted workflow, thus without losing the perceived benefits of using LLMs it can not be easily hidden. And the pattern isn't only about when but also what. You might be oblivious to it, but the pattern is very clear and not possible to mistake with regular code writing patterns in an overall project. It is harder to spot in individual smaller PRs though, but that isn't what Codeberg's new policy is targeting.

    And anyways, this isn't a question of "wrong-think", but simply of Codeberg not wanting to be associated with such low quality, likely copyright violating and resource hogging projects. The LLM using people have plenty of other code forges to use, so it is really a non-issue 🤷

  • No need to assume that. Just by using LLMs to assist with code writing, the human in the loop changes their commit pattern.

  • Sorry but you are clearly delusional. There is no magic involved, just being able to look at the structure of the code and the pattern of the commits. It's fairly easy in fact.

  • Well, in the case the OP referenced, it was impossible to miss, but I grant that the other dynamic blocklist that was found after I made the above comment is more difficult to notice as an admin.

    That said, Tesseract was forked from Photon for very unclear reasons, and that alone was a big red flag from the start that made me personally stay away from it.

  • Are you trying to make some point? Because, yes they can.

  • There are plenty of other public git forges you can migrate your LLM assisted projects to 🤷

  • You might not be able to tell, but the signs something is LLM generated are pretty obvious to more experienced programmers.

  • Yes, that is what the term "derivative work" referrs to.

  • Indeed, this ruling says nothing about something being a derivative work, all it says is that AI generated works can not create new copyright claims, which is totally sensible and non-controversial.

  • Looks like the bad HN commenter takes are leaking 😑

  • Those comments on HN are hilarious 😅 That site really works as a parody of bad tech bro takes if you ignore that most of them are sadly dead serious.

  • As long as Lemmy doesn't support password-less and revokable logins, no one should be using alternative web frontends hosted by someone other than their trusted server admin. And as this issue clearly shows, when an admin hosts it themselves the dev can't hide it and it is easy to circumvent.

  • …and the fact that their website uses AI generated templates, colours, fonts, call to action sure makes me believe that uncritically :/

    You check the source code of the website, or is that just the vibe that you get from it?

    I agree that my first reaction to the website was also that this might be AI generated, but on a second look it doesn't seem so clear to me.

  • Apparently not:

    We have a no-AI contributions policy. This is because, generally speaking, LLMs generate code that, while may work, is poorly organised and difficult to maintain.

  • They seem to have moved the client into the main repo.