I’m glad I saw this post and codeberg’s statement before the spam notifications.
I’m looking for a repo to host a couple of projects. I hadn’t considered codeberg as a home until now.
I guess I’ll donate when I sign up.
Exactly. I’ve already hosted a small script project there but this blog post reminded me I’d forgotten to add them to my December donations list.
Got two notifications this morning where I was tagged in an issue, but just a few minutes later when I tried to view the report it was already gone.
Really, props to the Codeberg moderation team for their hard work.I woke up to this, this is what it was if anyone was wondering:
edit: they’ve sent out apology emails to all who were affected. there was no leak of emails so it seems
I was tagged, immediately clicked to see the link so I could report abuse, and got a 404. Very fast response. I appreciate that and the message Codeberg sent out that OP posted here. Came to p.d to see if anyone posted it yet.
Seems like codeberg got significant attention for spammers to come and do this.
I currently have an outage from my own forgejo insrance (which codeberg runs as well afaik) since yesterday. I wonder if that is connected.
Here someone abused some feature to automatically create comments mentioning hundreds or more users so that the server send the comment notification via email. The email I got had just the N word followed by “balls” and lots of mentioned accounts. Not sure if others got longer messages?
That’s exactly what I got too
So that’s what it was…
More likely due to extreme AI scraping. That has been an issue with selfhosted Forgejo instances for months now and it is a complete PITA to deal with.
Time for the LLM crawler trap: https://zadzmo.org/code/nepenthes/
Is there an easier way to give them money than becoming a member?