|
|
|
|
|
by NoboruWataya
5 days ago
|
|
Interesting that the TOS contains the justification for the rule. That isn't necessarily something I would expect to see in a TOS and leaves the door open for people to dispute the justification or argue "well that's not relevant to THIS vibe coded project". Beyond the reasons stated I think there is probably a more general (albeit less tangible) benefit to having a forge with a reputation for being human-focused. Like if you see a project on Codeberg you can reasonably expect it's probably not completely machine-generated slop, which is no longer an expectation I have for GitHub. People are getting offended about it but why not just use a different forge for your vibe-coded projects? The main risk is that it leads to loads of distracting discussions about whether projects are "too vibe-coded" or whether they fall on the right side of the line. I would assume Codeberg would be relatively light touch about enforcement in marginal cases, which equally might blunt the effectiveness of the rule but ultimately, it doesn't have to be perfect to be useful. |
|
See also: 100MB per-user quota for repos that are not meaningful software.