← Back to context

Comment by skydhash

4 days ago

It does exists for any bank. Where I'm at, the assurance is given by the national bank, not the individual banks. Anything else is just probability and marketing.

In Codeberg case, what I would be looking at is the actual banning process, not "assurance" they won't ban me later. It's a Germany-based institution, if Germany applies a whole sanction to my country, I'm gone anyway.

4 comments

skydhash

Reply
saghm  4 days ago

> It does exists for any bank.

No one is disputing the existence of the question.

> In Codeberg case, what I would be looking at is the actual banning process, not "assurance" they won't ban me later.

Okay, so then, what actually is the banning process? The recent changes sound like the banning process has been expanded to cover a lot of new things that it didn't before, and stating "well anyone can ban you" isn't particularly helpful information, which was the point I was making.

  • skydhash  4 days ago

    > The recent changes sound like the banning process has been expanded to cover a lot of new things that it didn't before

    This is the actual part of the TOS

      Please be aware that this list is neither exhaustive nor complete (illustrating the spirit of the law, not its letter). Be aware that any account can get suspended at any time if it is used for activities harming Codeberg e.V. or its associated platform and services, directly or indirectly, even if these activities are not explicitly listed in the examples above.

    So anything goes. The actual list contains stuff that are going to get you expulsed for sure. But there’s nothing that guarantees your ability to host for a certain period of time.

    So your best bets is to keep backups of your data soemwhere else. Which you should always be doing.

    • saghm  4 days ago

      > So your best bets is to keep backups of your data soemwhere else. Which you should always be doing.

      Generally backing up a git repo is easy; it's all of the other stuff that tends to get hosted together with the code (issue tracking, pull requests, releases, potentially even CI) that's a lot worse to have to migrate over. Plus, anywhere a link was published to the repo is going to point to something that no longer exists.

      It actually sounds like we're in agreement for the most part about the relative levels of risk here. I misunderstood your earlier reply to me as a rebuttal to what I was saying to the parent commenter, but from re-reading it I'm realizing I might have inferred incorrectly.

      1 reply →