No, outages is when you start experimenting with local models and catch up what's new since last outage. If you're a power user, you end up getting to play with local models every week!
> If we are on the brink of Kessler Syndrome in LEO I would expect market pricing to reflect that.
Wouldn't the market pricing only reflect this after that fact? Up until it happens and no one knows any better, business will continue as usual because otherwise numbers don't go up. Like any past financial crisis, things look fine until they don't.
If it's using the same weird (and awful) "backend prompt encryption" pattern and mechanism that Codex also uses (https://news.ycombinator.com/item?id=48905028), then I'd also say it points to OpenAI being involved. Hopefully that shit isn't becoming a more popular pattern, absolutely awful for troubleshooting stuff.
> I predict that Codeberg will soon realize that they have no choice but to loosen and allow AI generated code.
I predict that eventually people will read the linked blog post and realize Codeberg already allows AI generated code. But this requires reading and nuance of course, which is hard to come by sometimes, so I guess we'll continue see misinformed comments like this until eventually the web is only autonomous agents.
Point out what verbatim piece of text forbids any and all usage of LLMs for coding and having that project on Codeberg?
Literally the first "informal guidelines" (subject to change of course) states:
> Projects who have an active community that cares about and maintains the software
You can use LLMs for development + fulfill this requirement, contrary to popular belief.
They want to get rid of slop projects and vibe coders, not any project that has any developer that used any LLM. But again, requires you to read through the actual text to actually get their intention here.
> You must not share projects that mostly consist of code written by "generative AI"-tools (including services such as Claude, OpenAI Codex). Such projects having an unclear copyright status (see requirements § 2 (1) 1 and § 2 (1) 3) and furthermore have little safeguards to ensure that they do not include harmful code (c.f. § 2 (1) 5).
I have read it. This effectively narrows down the use of AI drastically IMO. Which is what I said.
This effectively limits it to stuff like code completion and using it as a chat assistant and doing some medium level refactors.
They should have just completely banned it. As the ambiguity itself causes problems. Even if you use LLMs maybe say 25% of the time, sooner or later that means that a significant portion of your code base is AI generated.
> They want to get rid of slop projects and vibe coders, not any project that has any developer that used any LLM. But again, requires you to read through the actual text to actually get their intention here.
I am not a vibe coder (I am a software dev with almost 20 years experience) and am using Heavy LLM assistance (I am running Qwen 3.8 locally) for some of my projects. I am making sure the code output is decent, well documented, has tests etc. Sure what I am doing is something betweeen "vibe coding" and "proper development" but there would be no way for me in the few hours an evening to even get to the stage I would be at in some of them without LLM assistance.
I would not be able to use codeberg for hosting my project under their rules.
Remove/changing functionality in a way that the original use case you had for the device, no longer applies, because of a forced software update or user agreement you have to accept, should let people return the hardware regardless of when it was purchased. Bananas that this is still legal for companies to do.
Yeah, waiting for this too, feels like the final piece of the puzzle. Tracking issue from Codeberg + more general information about the effort around the the ecosystem:
Given how slowly it progresses in Forgejo, there are better alternatives - Radicle[1] (full decentralization, not a federation) and Tangled[2] (federation).
Man I was so excited about Tangled, until they announced they sought and got VC investments, which makes it not even worth looking into for long-term projects. I still wish them luck and hope they'll be the lonely 0.1% that can resist enshittification even during pressure from investors, but realistically my hope is fairly close to the bottom.
Radicle seems better in that regards, but instead is on top of their own cryptocurrency, which comes with its own issues.
Personally my best hope is still "real" federation across centralized services, ala ForgeFed, but ideally we can make all these approaches interoperate in the future, that would be really awesome.
Radicle is not based on crypto. The governance organization uses a DAO, but that’s not tied in with the project, only with the main dev team; it’s irrelevant to users. They had some early ideas to incentivize participation through crypto, but they abandoned it in alpha. I don’t know why this notion persists.
Personally I don't find the incentives of the only developer team working on something to be irrelevant to me as a user, if I'm looking for a long-term solution. Self-hosting/on-prem still seems like the only sensible solution here.
I think the notion persists because they are seemingly still using a DAO as the governance structure, so the organization sits on top of a cryptocurrency (is the idea of DAOs at least, in practice it isn't always so).
> Self-hosting/on-prem still seems like the only sensible solution here.
Radicle is self-hosted? Not sure what you mean by this.
If one doesn’t want anyone working on it to be crypto-adjacent, then I guess it wouldn’t be a good fit, but you can host and use it just fine without touching crypto yourself.
Did you actually read through that post you linked? You realize not every project that was ever touched by a LLM is being thrown off? Read the "Some early, but informal guidelines" particularly, as you've seemingly missed that.
They're targeting slop and essentially spam, not everything that could possibly have been built by LLMs.
> If you see yourself on this list, you don't need to move right away, but
there might be other places that better fit your needs:
- Projects written and maintained with heavy use of LLMs
All of the commits I browsed here seem to be LLM-assisted, so these projects are in this category. The policy being fuzzy is in itself a problem - "likely to be tolerated" is not a great policy to have your entire government depend on.
Personally, the refusal on "Projects heavily tied to the LLM ecosystem, e.g. LLM-written tools to ease LLM usage" is enough reason, as that's a good chunk of what I've been working on.
And that's not a bad thing. That's why they are communicating, so if you feel that is you and you're uncomfortable about it, you can move out and it's a win win.
Not everything should service all of us, especially not the smaller services. It's OK for places to have their own rules and them being upfront about this is a *good* thing.
No, the policy being fuzzy is a feature, because they're not 100% against all LLM usage, they're against slop and AI-spam, which is what they're trying to combat.
Laws are fuzzy, and we're doing mostly fine with this, of course there are edge-cases. But that's exactly why laws are fuzzy in the first place.
If you have a "automated software factory" or whatever the vibe-coders are up to today, then yes, Codeberg is probably not for you. But if you sit with a agent TUI in one tab, review things closely and don't just "throw code over the wall" without reviewing it, you have nothing to worry about with hosting code on Codeberg.
Interestingly enough, you could read the domain as three separate parts ("echo", "hive" and "ai") and every single one of them somehow reads as AI basically. It's like someone asked an LLM to come up with a name that sounds as much AI as possible, and it put those together.
I can understand how you might feel that way. this was the name of one of the first text to image apps I built 4 years ago with one of world's first auto prompt enhancement with a fine tuned currie model
I think projects that seemingly don't even use Semver (putty uses two instead of three numbers), and also were created before semver was even a "concrete thing" (~2010?), gets a pass on the requirements that semver proposed, like the whole "1.0.0 means stable and in wide use" thing.
Semver or otherwise, I think even decades ago people understood staying on 0. for years or decades is a bit silly for production software tens of thousands of people use every day.
Doing pacman -Q | grep ' 0\.' locally I get 547 hits, with alacritty, bubblewrap, dconf, fzf, hyprland, mtr, neovim and more among them, software that is in wide use already, some of them quite old (dconf apparently almost two decades old).
I think people read too much into what is just a number for some projects, while for others (like semver zealots), the numbers carry actual meaning.
> In a similar vein I made a site to check local water quality and swimming conditions in the Bay Area.
Not to rain on anyone's parade here, but if we have to check the results on the official agency postings anyway instead of relying on what you put on the website, what's the point of the website in the first place? Kind of feels like either own up to that you get the data import right, or don't bother at all. Maybe I miss the point though?
reply