Codeberg going down the path of Blueskyification
[flagged]
LLMs are here to stay. The genie’s out of the lamp. Get over it.
161–170 of 242 posts
Earlier quoted context omitted.
I've been thinking along these lines more and more. Trying to specify exact limits and trying to account for every possible situation when making rules just encourages people to find holes and workarounds. It creates a game, a competition between the rule makers and everyone else. When instead you state higher level values and ask for cooperation, it encourages us to work together. It's the Honor System instead of a…
> there's no referee, most everyone does their best to just play hard and follow the rules Only in small groups. Any sufficiently large groups will have a number of people (possibly sociopaths) that will break the rules for personal gain. And in a lot of cases it's enough if very few people do that.
Earlier quoted context omitted.
> 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 pa…
> 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 servic…
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.
I think this move by Codeberg is lowkey genius. They're trying to build a community based on a set of shared values. Those who disagree with those values are now self-selecting out of the Codeberg community, which is exactly the point of passing these kinds of resolutions. The fact that the rule is open for interpretation means that they can effectively shut down malicious actors (i.e those who intentionally misrepre…
Reminds me of internal political disagreements.
Earlier quoted context omitted.
They didn't consult a lawyer when they wrote that. The idea that public domain code that is not copyrightable is incompatible with the GPL is simply not true. sqlite is in the public domain and not copyrightable, for example. Their decision leans too heavily on what that court decision said. It was actually fairly nuanced. The court explicitly declined to address whether Thaler could be considered the author because…
> sqlite is in the public domain and not copyrightable, for example. And therefore is not licensable under the GPL; because no license is needed at all. Ardour's goal isn't to be "compatible with" the GPL (in the sense of allowing binaries to be built containing both GPL-licensed code and their own code); their goal is to be covered by the GPL license for the purpose of constraining what actions users can take. This…
I think this move by Codeberg is lowkey genius. They're trying to build a community based on a set of shared values. Those who disagree with those values are now self-selecting out of the Codeberg community, which is exactly the point of passing these kinds of resolutions. The fact that the rule is open for interpretation means that they can effectively shut down malicious actors (i.e those who intentionally misrepre…
Based on this precedence, if I'm accepted into the community today, how would I know I'll be accepted tomorrow? If you're literally just using Codeberg as a mirror, then sure, it doesn't really matter much. But like you said, that's not what they are building. They want people to invest in the community. So now, as an investor of my hard-earned free time, I'm faced with the question on whether all my investment can g…
Earlier quoted context omitted.
> 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 servic…
> 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…
> 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.
I think most of them provides API endpoint to access those data or some export tools. And as far as links go, I would prefer to have a webpage for any relevant projects, something like the one for msmtp [0], tied to my own domain.
Codeberg going down the path of Blueskyification
Bluesky, from my daily use, seems like it’s thriving and full of varied and interesting people.