Post #2913177

Are you looking to fearmonger about non-existing RCEs and drop a carrot disclosure (https://codeberg.org/forgejo/website/issues/839#issuecomment-14208296)? Please don't do that; contributors also want to sleep at night. Still, Forgejo doesn't need to know where its security could be tightened and hardened; we have a good list of issues with the security label for that (https://codeberg.org/forgejo/forgejo/issues?labels=79184&state=open). It does need people's valuable time to go and work on that and feel rewarded by doing that kind of work. Forgejo has localization for a good number of languages. https://codeberg.org/0ko/ has gone to great lengths to improve Forgejo in this area and is thereby allowing translators of many languages to translate Forgejo in the best way possible for their language. We do have a massive bias for majorly translating it to European languages. At least we're not like GitHub, which is fully committed to not caring about this at all (https://github.blog/news-insights/the-library/github-in-your-language/). We gladly welcome new translators for any language and help in making an RTL layout in Forgejo. https://forgejo.org/docs/latest/contributor/localization/ We build official Forgejo (Runner) binaries for x86_64 and ARM64, but we only have CI tests on the x86_64 architecture. There's no opposition to starting to test arm64 and producing binaries for RISC-V if Forgejo had their hands on a server with that architecture. Unfortunately with AI-caused resource speculation, getting hands on affordable new hardware is challenging, even renting is seemingly no longer a viable option. https://matrix.to/#/#forgejo-infrastructure:matrix.org