Hm... so this new AI thing from @gitea ... it's definitely interesting, and many people aren't reading, again.
So, what did they do?
They basically created an API client that is usable for LLMs - meaning that LLMs can now directly interact with Gitea. It's not integrated into the server by itself, and nobody is required to use it. Basically, it's HTTP 
MCP. It's like an API client for a programming language. So it's not a bad thing in itself.
Also, this client by itself doesn't crawl other sites / uses data that was crawled from other sites, since it's literally just an API client.
BUT (!) you have to use an existing LLM model using a client (e.g. Cursor) to be able to use this API client. Now that's the interesting part... I don't know if there's actually a good LLM that only learned from data that it was allowed to use. This means, that Gitea kind of promotes using LLMs that crawled people's sites without their permission.
Sadly, the screenshots shown in the blog post by Gitea don't show what model they are using, so we can't tell if they are using a good or a bad model. (Though, I'm not sure if we specifically need to know that in this case.)
Anyway, I'm always happy to see people switch to @forgejo. I, personally, used it almost since I started moving away from GitHub / -Lab and I love it. Sadly, I know a few people who can't yet move to Forgejo since they're using architectures that Forgejo doesn't build for docker yet.
For those people who are still angry and "need to" be aggressive towards the devs: Calm down, maybe read my blog post that I made in collaboration with Finnley about outrage (https://steffo.blog/outrage-warps-reality/) and have a great day. Maybe go for a walk outside?
Anyway, have a lovely day! 
It is a high level overview of the project activities.
