They're not banning code written and maintained with the use of LLM's. They're banning projects entirely created by LLM's and heavily (or solely) maintained by LLM's.
It's basically not allowing junkfood on their platform. Now that code is easier than ever to barf out, so will the amount of junk.
As for tossing out any and all crypto projects... how is anyone still willing to associate themselves with that pile of garbage?
I tend to agree but you can't deny that the widespread use of LLMs means that codeberg will expend more resources overall for projects taking advantage of them. And its members have spoken. We might disagree about the conclusion they came to and even how they went about it but their stance is clear now so we might as well just move on.
Yeah but if it's about the hardware resources, why not just establish an option to ban projects that use them unreasonably for their projects relevance? In their explanation they say each project will be evaluated individually and the whatever-AI-allegations are not the primary reason to eventually ban.
They could have established a direct way to protect hardware resource with an option to ban users that cause unreasonable load. Maybe not great but understandable considering they are an e.V.
It is already like that. They aren't hooking up an LLM detector to the ban button. They are saying this is grounds for human-triggered enforcement action.
we should also flag any projects to do with the enshittification of the world. Probably banning all JS, node, bun, loaf or any other related projects would be good.
Since we're talking about my opinions here, which should be construed as laws of my hosting platform, i always hated ruby so lets ban ruby.
In fact codeberg shall only accept Perl programs going forward that are written using emacs
Duckduckgo is blocked in my country. Reddit is blocked in my country. My country is also one of first countries agree to ban free (non playstore) android app installation. My country is so against freedom. What a shitty country.
Good thing about rust is it forces you to write code in disciplined manner. I remember myself fighting those rules. Until it becomes natural to me and I can detect why the compiler rejected my code without reading the compiler error (for a simple one of course, but not syntax error). And that habit of carefully writing good code without slowing down carries over when I'm writing code in other languages.
I just realized how powerless we are. The situation is almost unavoidable. Majority people will just accept this. They are unaware how restricted they are, thus they don't care.
are there enough devs to make "non-certified" phones? also i wonder if you'll be able to disable the verification check similar to bootloader unlocking.
Non-certified phones won't be sold in Western markets. This whole scheme has one goal only, and that's to snuff out DRM-unfriendly third party apps like alternative Youtube clients, videogame emulators and P2P file sharing apps.
They're being sold and enough people are buying them to keep these companies alive. Fairphone said they're not delivering to USA because they don't have the manpower, not because there's no demand. Every release again you see people asking in the comments when/if it'll finally be available to them
That's not to say it's a big market where you get big economy of scale benefits. The devices are expensive but they're yours (and some of them try to do ethical resource mining and/or pay fair wages as well). Some of these will also have Googled variants available, but it's a choice
They don't have the manpower to drop off some USA-bound boxes at the same shipping carrier they use for their EU deliveries? I highly doubt that. They likely don't want to bother with FCC approval, opposition from Google about selling de-Googled Android or produce separate SKUs for US-specific 5G frequencies.
what i'm saying is it's time to make a new company. this is a matter of maintaining good technology and avoiding enshitification so it's quite important.
That's my point. Who is going to create a company to compete with Google and Apple on the smartphone front? They already ran everybody else out of business (Palm WebOS, BlackberryOS, Windows Phone). The alternatives are already here but they don't operate in North America (Huawei HarmonyOS, Jolla OS, Pinephone).
yeah that's what i'm saying. but obviously the problem is funding.
so do we have enough engineers who care about maintaining useful tools that aren't handicapped or compromised to be able to support this endeavor? i think we do. there have to be many good eggs within these companies who die a little inside each time something like this goes through.
> They already ran everybody else out of business (Palm WebOS, BlackberryOS, Windows Phone).
Only because those alternative mobile OSes were, frankly, crappy in comparison to iOS and Android.
I don't recall Google or Apple doing anything particularly anticompetitive to cause any of those OSes to fail to keep up in the market, aside from just plain "being the 800lb gorillas in the room". (Not saying they never do anything anticompetitive, just that those particular market failures can't be laid at their feet.)
It would be great to have some really good alternatives to the mobile duopoly. Hell, if we had more fragmentation in the market, that would even lead to more impetus for interoperability and common standards—which we desperately need more of everywhere in tech these days. But those three, in particular? They lost because they were worse at being a good mobile OS for most people.
Sadly "non-certified" phones come at a big consequence, I wrote a big article on it on HN but I'll give you the summary, Google has added in "play integrity" into all certified phones which detects if your bootloader is unlocked or your phone is modified in some way, and apps can (and do) request this device verdict on your device to choose to deny you service. Bank apps, basically all NFC wallet apps like Google Wallet, and games do this, and it's a massive headache. Good apps also make this a server-side check meaning you cannot bypass this without leaking your phone's special hardware attestation key stored in 50 different layers of security in the actual CPU with tamper detection.
