Following our transparent model and our obligation to protect the platform (and in this case possible other people interacting with this user/company), we’d like to share the following discussion which happened after a user account restriction during the last week.
Here’s a recap of the situation:
-
2026-04-13: We got alerted by a disk space issue on the platform by our monitoring. During inspection we realized that a specific account (AmanoTeam, 88 repos) has exceeded the storage quota by a lot. The main issue was a (meanwhile deleted) mirror of the binutils project. The repo was not set up as a Forgejo mirror but an external process pushed updates to the repo there manually. However, the first push never succeeded as the content body was too large, leaving behind ~500MB of incomplete files on every try. The automation tried repeatedly to push, eventually increasing the (incomplete) state on disk by 500MB on every push.
-
After having identified the issue, we garbage collected the repo and deleted it (since it was empty anyhow). We contacted the user under the available email address, but didn’t get any response for the next two days.
-
We noticed that the account has more repositories that were acting as de-facto mirror and even a repo which controls this mirror functionality. On top, the user hasn’t had logged in ever after their initial creation and no interaction with the platform happened. This makes it look like that the user is (ab)using CF only as a secondary pull mirror to circumvent rate limiting on other platforms or similar.
-
2026-04-16: The user again created the
binutilsrepo (through create-on-push) and failed to push again with the same error as reported previously. At this point we had to take a decision to both enforce a reply from the user and protect the platform. Hence, we put the user into “restricted” mode, which means that it can’t push/pull anymore. -
2026-04-19: On this day we received this email:
Hey, I’ve just noticed that you suspended the account which was pushing the repositories to your Forgejo instance, which was set up by a team member of our company, even AFTER we deleted all 3rd party repository mirrors, like glibc, binutils, fdroiddata, bearssl and etc, which were the biggest culprits of space usage.
I was thinking about donating to your project, since it benefits the open source community, and even maybe sponsoring your service via our company, but after this complete dick head move, you can completely delete the user instead, we don’t care about your shitty service, since there are more serious projects such as Codeberg, which hasn’t done anything similar.
About the donation, we donate when we feel like you’re giving a good value for us. Doing this doesn’t give us a shit. It’s a better idea to pay that value to buy a cheap VPS and host a Forgejo instance on our own then, which we did: https://git.amanoteam.com
Kindly fuck you, thanks.
-
So the user finally noticed that pushing doesn’t work anymore and then checked their mails. A few comments on their reply:
- We didn’t suspend their account after they deleted the mirror repos, it has been suspended before.
- There was no other communication from their side asking for an unblock or mentioning their actions. Instead they decided to insult is directly (see mail above).
-
A few hours later, another representative of the company added a follow-up reply:
My colleague went ahead and shared his opinion on this (you can assume that most of his thoughts are also shared by the rest of our team members), and I already considered the matter to be settled there. However, I would like to add that, despite the restrictions applied to our account, our repositories are still publicly listed on the website.
I kindly ask you to remove the remaining repositories and also delete our account from your system, since we do not want to have ghost projects living in a random place we no longer have access to. It would also be a shame if some of our users went there asking for support only to be left without a reply.
Cheers,
Thomás Thurbando Pinto.
Our reply to this (2026-04-20) was as follows:
We reached out to you upfront to clarify the issue. You didn’t respond to it and continued to push to the mentioned repos.
The logical next step is to restrict your user therefore.We could have easily unblocked your user after clarification and adjustments but you decided to escalate this immediately instead.
CodeFloe is a development platform aiming to provide a fast and enjoyable Git experience for anyone for free, within reasonable resource limits - it is not aimed being abused as a secondary pull/push mirror for large assets without interacting with the platform per se.About the donation, we donate when we feel like you’re giving a good value for us. Doing this doesn’t give us a shit.
It’s a better idea to pay that value to buy a cheap VPS and host a Forgejo instance on our own then, which we did: https://git.amanoteam.comdon’t care about your shitty service, since there are more serious projects such as Codeberg, which hasn’t done
anything similar.Codeberg doesn’t allow any mirroring at all, but of course you are aware of this.
Please note that we will publicly share your reply so all users know what is going on and get an idea of how your company reacted to this matter.
Additionally, we might also take legal action if you continue to insult us or take any other harmful actions against CodeFloe as a platform.Best regards
Companies:
- https://amanoteam.com/ (LLC, Brasil)
- https://tuta.com/ (added as CC in mails, Germany, redirected from tutanota.com domain)
Acting people:
- alissonlauffer (Alisson L.) · GitHub , Website
- Thomás Thurbando Pinto