[free_bip]

You are effectively saying you do not trust the judgement of the community to accept you long term.

Why is that? Is it because you believe there would be a new policy that would exclude your workflow? What would such a policy be? Do you really, reasonably believe it would be implemented "tomorrow"? Do you think adapting to such a policy would be unreasonable?

Or is it because you don't trust the judgement of the people enforcing these new rules?

If not one of the two, what is the reason?

The point I'm trying to make here is that this just sounds like a slippery slope argument. If you don't have a concrete reason to believe you won't be welcome "tomorrow" then my mind has not been changed.

[aliasxneo]

> You are effectively saying you do not trust the judgement of the community to accept you long term.

Correct. I was previously engaging with this community and had moved some repos over from GitHub. One of those repos deals with cryptography that has an intersection with "crypto" projects. Due to vagueness of the language ratified, it's unclear whether the repo now violates the ToS. This completely caught me off guard, and now my trust in the judgement of the Codeberg community has been weakened.

This feels like a reasonable reaction to me.

[inigyou]

So it sounds like you're treating Codeberg as a neutral git host. They've made it clear they don't want to be that, they are a charity association that supports free software development by providing free software developers with services like git hosting. They are not wasting their services on people who don't align with the mission.

[free_bip]

That seems like a completely different concern than what you originally stated? You're not worried about future policies, you're worried about the policy that was just passed.

And for what it's worth, it seems like they only care if the project is directly crypto related (e.g if you had a repo directly implementing a Monero node, that would probably not be allowed). If it's just a repo that implements a generic Cryptography concept that happens to be used both in crypto and elsewhere, then I don't see what the problem would be.

Again, the rules are judgement based. That means you can interact with the community to get clarification, and make your case that your project is worth keeping.

[aliasxneo]

> That seems like a completely different concern than what you originally stated?

I started with a hypothetical. Then I used an actual real-world example. I have 100+ repos on GitHub spanning a wide array of technologies. If I moved all 100+ over, how do I know I won't fall afoul of whatever the community votes to ban next?

The point is Codeberg isn't a good fit for my situation which needs more continuity and less surprises, and that's been made readily apparent now. So I'm leaving, just like many other people who have been posting about it.

[free_bip]

Luckily for you, as far as I can tell you don't have any concrete reason to fear having your repos taken down. Or at least I haven't been given any.

If the reason is more emotional than rational ("this feels like it's going to change more"), that's okay. Not everything needs to be governed by rigid rules. The Codeberg community knows that well. If in a few years your 100+ repos are still all fine and dandy to their rule set I'm sure they'd be happy to have you.

[aliasxneo]

> Luckily for you, as far as I can tell you don't have any concrete reason to fear having your repos taken down. Or at least I haven't been given any.

Unfortunately you can't make that decision. I have to wait and find out how far the ToS violation will be implemented. Or I just avoid that stress and go somewhere else. Most people being affected seem to be choosing the latter.

> If the reason is more emotional than rational

That's a bit reductive. Risk management always has a level of uncertainty involved. No one makes decisions with 100% certainty in the outcome. Before these votes, I had a certain level of risk assessment in moving off Github To Codeberg that favored Codeberg. Now that situation has changed. It's not "emotional" to recognize that.

[mariusor]

Have you considered actually asking someone at Codeberg about your cryptography project?

[theshrike79]

Who would one ask to get an official and enforceable answer?

I don’t want an opinion, I need a definitive ruling I can trust.

[mariusor]

It's not like they don't have a contact page: https://docs.codeberg.org/contact/

> I need a definitive ruling I can trust

Why? What's so special about the place where you host your source? It's the second time I see this sentiment in the thread, and I don't get it. If an official channel tells you a project is OK, and then someone else decides it's not, what does it really happen outside of you taking your project elsewhere?

[warkdarrior]

Is this the "contact our sales team for pricing" of open source?

[inigyou]

no this is the "we are real people, not a faceless algorithm" of open source.

[cge]

>And for what it's worth, it seems like they only care if the project is directly crypto related (e.g if you had a repo directly implementing a Monero node, that would probably not be allowed).

Looking at community conversations, there actually seems to be little clarity over this, and quite a bit of confusion. Several established members of the community seem to be saying that the ToS actually only bans "cryptocurrency related projects" that "[harm] the reputation of Codeberg", and that direct cryptocurrency projects that don't harm Codeberg's reputation are actually allowed, saying that the current banner is a mistake and is in the process of being changed (while they have their own systems and are not on Codeberg, I'm guessing GNU Taler might be an example of a cryptocurrency project that would be allowed). In fact, this appears to be within the official interpretation used when locking the discussion thread on the change ([1] refers to [2]).

[1] https://codeberg.org/Codeberg/org/pulls/1254#issuecomment-19... [2] https://codeberg.org/Codeberg/org/pulls/1254#issuecomment-19...

[johnfn]

I think the burden of proof is on you to argue that Codeberg will stop at exactly two policies, given they haven’t said they will do that, but they have already banned things they don’t like. A slippery slope argument isn't a fallacy when you've already slipped down the slope twice.

[aliasxneo]

I really don't understand the argument, to be honest. If somebody is participating in something with a perceived expectation, and then that expectation gets contradicted not once, but twice, why is it unreasonable to assume it might happen again? I'm not being facetious, I genuinely don't understand the line of thinking.

[johnfn]

I think I agree with you, so maybe you meant to ask someone else? Or you’re just supporting my argument, in which case I appreciate it :-)

[card_zero]

If they have a coherent set of values, then that's why. Then you have a theory of mind about the admins, and they weren't behaving erratically, but it was your original expectations that were incorrect.

[no-name-here]

Codeberg has existed since 2018. Was it clear to you a few years ago that things like 1) projects tied to AI, 2) mostly AI code, and 3) crypto would be banned? If not, then what makes you believe you now know their future actions if you didn’t before?

[Lerc]

If you consider the argument of the comment at the top, that those who disagree with banning will leave. It would seem that you could expect an acceleration.

I have actually seen, from the inside, organisations implode though ideological purity demands.

No two people believe in all the same things. In the end this path reduces to one single shared value, That those with different values should be excluded.

[nmz]

They won't. No company will, I think the best quote I've heard this week is from the proton CEO on the Decoder podcast.

"No company is going to jail for you."

If vibe code is of questionable legality, then the best thing to do is to remain guarded until its legal standing is determined. It is simply an added bonus that it prevents slop that consumes data on servers for projects that nobody cares about enough to not have vibe coded.

[mcv]

Codeberg is not a company. Also, we're not talking about jail. We're talking about principles.

[no-name-here]

> No company is going to jail for you.

Are you arguing a Codeberg member had a legitimate fear of being jailed for hosting others’ AI code? And GitHub/all other hosters should have the same legitimate fear of being jailed a long as they don’t ban the same? Or is this more of a straw man? Or were you bringing up that quote to point out that those trying to defend Codeberg are using completely fabricated arguments?

[cge]

Honestly, for me, both.

While I can't find something specific about it in the new ToS, the new blog post notes that "side projects and experiments", and "specific tools and custom scripts that would be unlikely to find a community anyway" are "discouraged", but are "tolerated in practice" if they only use minimal resources. This is stated as being regardless of LLM use. So some of my repositories are apparently already borderline in the community's opinion (it's not clear how they judge use of resources, but I only use self-hosted runners).

But there also seems to be an increasing sense that many active members see Codeberg as a space for a particular type of FOSS, within a particular, normative view of what development and communities should look like. This ties into the "side projects and experiments" comment, and to the general tone of the AI blog post on what they want Codeberg to be and not be. The point about "projects with a single developer and virtually no users", about "large ghost projects", and so on, are within the context of AI, but are derided in a wider sense.

Some of my repositories look like single developer experiments with no users or community, but aren't. I'm ultimately a scientist, not a typical developer; users typically communicate by email and at conferences, and cite my software and associated papers in their papers rather than starring repositories on forges.

And yes, much of the discussion around these questions often falls into the argument that projects that are good will be fine, because they'll be accepted despite the rules, and that any concern about specifics is unwarranted. But I can't know that I won't be targeted by Codeberg having an increasingly normative view of what 'proper' community development looks like.

(Yes, I realize I'm free to use something else. I'll likely end up moving my repositories off Codeberg and onto some combination of my own Forgejo instance and Github. The lack of federation in Forgejo heavily penalizes not being on a major instance, however. Meanwhile, as much as I encourage using DOIs for citations rather than URLs, people often do the latter, so staying on an instance that might decide to ban my projects can create lasting problems: one of my whole reasons for starting to migrate to Codeberg was because it seemed organizationally stable.)

[yuriks]

My read of the "side projects and experiments" part of the blog post is that, in the context of LLM projects, if your project does not use resources and isn't looking to attract a community then, if only due to the practicalities of moderation/enforcement, they're unlikely to take any action against it because it won't be visible or causing enough problems.

[cge]

Asking about this, it seems like that might be the case: they likely intended the "even if they were not LLM-generated" to be counterfactual. It's an unfortunate place to leave such grammatical ambiguity.

[mcv]

Is it not obvious? They've just done it. They've excluded people based on new rules, and not everybody was expecting those new rules.

Having done it once, they can clearly do it again. Will it be justified? Who knows? Will it exclude you? Maybe.

[p2detar]

> You are effectively saying you do not trust the judgement of the community to accept you long term. Why is that?

I think the blog post explained exactly that. To quote:

> The actual wording makes this more difficult. The terms prohibit projects that mostly consist of code written by generative AI tools. In an actively developed codebase, what does “mostly” mean, and who can still tell? I could not reliably assign authorship percentages to many of my own recent projects. The line is open to interpretation precisely where it needs to be enforceable.