I did when I first saw the change. Then I decided to do something about it and spent the day moving my stuff to my own self hosted Forgejo instance.
Now Codeberg is free to do as it wants as am I.
I regret migrating to Codeberg
251–260 of 617 posts
Re: I regret migrating to Codeberg
#252A little bit offtopic, but I spend 12 USD a month for a 1 high performance core, 2GB ram, 50GB NVME SSD VPS, and slap nginx and cgit config on there, and host my own git repos. I realize this doesn't work for everyone, and not everyone has the money to spare, but it's really nice to be able to host your own stuff on your own website, and not be tied down to a forge like github or codeberg. Bonus points if you have th…
How is it bonus points if you host at home? My big fear is that a fire, etc deletes my data. You're going to need that extra server whether you like it or not.
[deleted]
Re: I regret migrating to Codeberg
#253Keeping up with this stuff is for people who define their identity through virtue signalling and whatever personality trait they have decided to make the problem of everyone around them. Let them have their little corner of the internet and just stay away. There's plenty of alternatives run by people who don't feel the need to bring their personal baggage into a cooperative environment.
[deleted]
Re: I regret migrating to Codeberg
#254Earlier quoted context omitted.
So I voted against, partly because I feel that the text doesn't to justice to such a multifaceted topic. If all projects on Codeberg were human-written, that would be a big seal of quality! There are a lot of projects coming out now where someone feels like they've made a cool thing but it breaks on the first edge case and is entirely unmaintainable. Many are built on wrong principles because the prompt authors aren'…
> imagine LLMs got twice as good as they are today) I have no idea how you'd quantify that, but they're pretty good already. At least in the hands of someone who knows what they're doing. I share everybody's concern about many aspects of LLMs; copyright, data collection, energy use, component prices, not to mention what it does to us: outsourcing our thinking, dependency, slop. And I don't entirely disagree wanting t…
> No idea where yet; I don't want to go to Github, and I believe there were similar concerns about Gitlab, so I don't know where to go yet.
Perhaps https://radicle.dev or https://tangled.org would be fine for you?
Re: I regret migrating to Codeberg
#255Keeping up with this stuff is for people who define their identity through virtue signalling and whatever personality trait they have decided to make the problem of everyone around them. Let them have their little corner of the internet and just stay away. There's plenty of alternatives run by people who don't feel the need to bring their personal baggage into a cooperative environment.
[deleted]
Re: I regret migrating to Codeberg
#256Earlier quoted context omitted.
How does Bluesky or ATProto prevent that power trip?
I'm not going to do the protocol justice in an HN comment, but a core goal is to separate the entities that control the data, the entities that run the network, and the entities that control the interfaces (and recommendation algos etc). If your Mastodon admin goes rogue, you a) have to get your data out of their hands, and b) have to rebuild your Mastodon presence in a new location, all your connections, history, et…
But if you are going to self-host, then you can also self-host a Mastodon server and never have to migrate anywhere; wouldn't that achieve the same effect?
Re: I regret migrating to Codeberg
#257The new terms [0] say “You must not share projects that mostly consist of code written by "generative AI"-tools […]. Such projects having an unclear copyright status […]” So okay, if you're concerned about the risk of liability from unclear copyright status, I suppose that's fine, but then why the “mostly”? It's not like the copyright status becomes less unclear by you supplementing with 50% hand-written code. [0] ht…
> then why the “mostly”?
Because it's all vibes, all the way down. Vibewritten rules, vibenforced. If they get bad vibes from your project, they kick you out.
Re: I regret migrating to Codeberg
#258> It seems like many ‘vibe coders’ don’t realize that they don’t actually have a community around them. This is not about demanding a community, as the article argues about at great length: it's only a polite way to say that many ‘vibe coders’ are annoying, negative net value assholes. Community would ensure that they are not aberrant lone wolves.
> many ‘vibe coders’ are annoying, negative net value assholes Where on Earth does this sentiment come from? I've had people make AI contributions to my open-source projects and while they may be perhaps less technical on average they're every bit as well intentioned - possibly moreso since they're interested in improving the project rather than establishing a little fiefdom.
Well I think they are probably well intentioned and annoying... and possibly net negative but I'll reserve judgement on that.
E.g. I've had people find genuine bugs and then basically paste their entire Claude conversation into the issue. Very annoying.
Re: I regret migrating to Codeberg
#259If you wants to make their own forge where LLM-assisted work is prohibited, go ahead. Waiting for people to go all-in on your service and then kicking them out however is frankly rotten thing to do; but entirely expected of Codeberg, which is more a political community than a useful forge.
Re: I regret migrating to Codeberg
#260> In addition, Codeberg conflates “having a community” with “being legitimate software worth hosting” I don't think this is a fair summary. I don't see this conflation in Codeberg's blog post. The words in quotation marks don't actually exist in Codeberg's blog post. It seems that what they are saying is: In a free hosting platform where we share all the resources, it's not fair that some people using LLMs are using…
Define resources and create a better limit then. 10 small code-only projects will take orders of magnitude less storage, bandwidth and cpu than one project with committed image and sound assets.
And as long as it's hand-made, that's fine.