> 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 up disproportionately huge hosting resources to handle the unnaturally large amounts of resources they can churn out with these tools.
Then instead of addressing the excessive resource usage problem indirectly via banning AI-assisted apps, they could've addressed it directly by imposing limits/quotas.
It's abundantly clear (and not that they are hiding it either) that their issue is with AI itself so anything else is just a secondary concern if not even a smokescreen.
---
> I'm a solo dev, and I couldn't find the judgement against solo developers or any slight against people who don't have a team.
Quoting their blogpost [0]:
> ## The development team of none
> Using LLMs to work with your code gives you a kick of adrenaline. You can develop at a rapid pace, build things as if you had a large team. Only that you have none. In fact, you are (often) alone, working with a statistical machine that turns energy into code.
I couldn't care less about what they think about solo developers, but it's just one bad excuse after another and that's what people are criticising. Open Source is one person. [1]
> The author seems annoyed that Codeberg wants to focus on projects that have a legitimate contributor community and is not designed for one-off individual projects.
I think Codeberg was never intended for one-off individual projects in the first place, such as them discouraging private repositories. Quoting their Terms of Use [0]:
> Private repositories are only allowed for things required for FLOSS projects, like storing secrets, team-internal discussions or hiding projects from the public until they're ready for usage and/or contribution. [...]
And this makes a ton of sense, because Codeberg is a community-funded volunteer-supported non-profit, and it doesn't make sense to spend their resources for repositories that don't benefit the public.
I think "legitimate contributor community" is just an excuse so I am not going to dwell on it. From Ghostty to Redis, rsync to Linux kernel, more and more FOSS projects are taking advantage of various AI tools in a responsible manner and closing the door on them is just unfortunate and backward in my opinion. We gain nothing from this change and lose a ton of progress in software freedom and digital commons.
> It's not all that different from Mastodon instances. It's a community space, and the community gets to decide who they allow to use their resources.
Of course, and the bigger community gets to discuss their decision. :)
> It's interesting because the terms have repeatedly stated that using them isn't banned
This is the relevant part in Codeberg's Terms of Use: [0]
> 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).
The only ambiguous part is what "mostly" means in practice, but otherwise the Terms of Use is pretty clear. I'll admit that their blog post [1] is more inclusive and tries to clarify things but it's all just one very unnecessary drama [2].
You can use fuse-btfs [0] for mounting torrents as filesystems! Last I checked it was a fairly mature piece of software so hopefully it doesn’t feel unnatural.
I think the biggest sin of IPFS is not working natively in web browsers—instead, requiring the use of either HTTP gateways or native apps running outside the browser.
Is anyone still (or has anyone ever) used IPFS in production?
I’m not talking about technology demos such as Wikipedia-on-IPFS (which indeed worked and was impressive) but where IPFS is actually being relied on for some functionality.
For macOS and iOS, you can create a profile to configure which DNS server you want to use at all times (including across different Wi-Fi networks and mobile data). See:
> TPB has become an institution that people just expected to be there. Noone willing to take the technology further. The site was ugly, full of bugs, old code and old design. It never changed except for one thing – the ads. More and more ads was filling the site, and somehow when it felt unimaginable to make these ads more distasteful they somehow ended up even worse.
> As a big fan of the KLF I once learned that it’s great to burn great things up. At least then you can quit while you’re on top. I think I left TPB just a little bit after that top, and not when it’s as shitty as it was when it was closed today. It feels good that it might have closed down forever, just a real shame the way it did that. A planned retirement would have given the community time and a way to kick off something new, something better, something faster, something more reliable and with no chance of corrupting itself. Something that had a soul and could retain it.
I think this HN submission provides little value and a lot more headache to the maintainers of FOSS project (you can already see a lot of brigading in the GitHub comments). IMHO HN shouldn’t allow submissions like this.
Developer, Amateur Photographer, and Human After All.
bora at boramalper dot org
https://www.boramalper.org
https://mastodon.social/@boramalper
meet.hn/city/51.897077,-8.4654674/Cork