CodeFloe

@badsector

Should be working now! Let us know in case you encounter further problems!

@badsector That shouldn't be, thanks for raising it!

This is caused by our HAProxy ACL rules denying access if there are too many query parameters in the URL - which is what happens if you visit these paths as FJ will insert something like

$URL?q=&type=all&sort=relevance&state=all&labels=&milestone=0&project=0&assignee=0&poster=0&archived=false

We'll fix it and relax our ACL there. It's always a thin line between gating unwanted traffic and not affecting real users :)

@hmiron @Tronde

Appreciated!

Our cost matrix is fully public and regularly updated. See here: https://codefloe.com/codefloe/analytics/src/branch/main/reports/costs/cost_summary.md

@Tronde

We accept donations. Thr goal is reach cost parity at some point. We haven't done so since the platform is up and see the effective costs as a service to the public ✌️
After parity is reached, the remaining funds will be given out to the individuals maintaining the platform.

Now that #codeberg has manifested their anti-AI view with a 70% in favor vote (https://codeberg.org/Codeberg/org/pulls/1253), we're happy to welcome (once again) all the people which have to/want to move their repositories off Codeberg but still want to stay on a Forgejo-based instance.

Bonus: on top you'll get better uptime, faster site responses and faster CI runners - all for free :)

tl;dr: after this ToU change, keeping AI-generated code on Codeberg would violate these and repositories will be in danger of deletion.

#codeberg #codefloe #giveUpGitHub