Codeberg/Community
54
325
Fork
You've already forked Community
12

Forum spam #1878

Closed
opened 2025年04月24日 08:21:40 +02:00 by timurmobi · 8 comments

Comment

Hi. In the last hours I received forum spam from several bot accounts. The posts look almost kind of real, which is bothering. Maybe a limit to the number of new issues a user can create (per hour?) can solve this to a large extend? Most users do not need to create many issues per hour. Thank you.

### Comment Hi. In the last hours I received forum spam from several bot accounts. The posts look almost kind of real, which is bothering. Maybe a limit to the number of new issues a user can create (per hour?) can solve this to a large extend? Most users do not need to create many issues per hour. Thank you.

Yes.

I appreciate Codeberg for fighting hard against these orchestrated attacks. We just saw a big number of accounts who each created hundreds of issues within hours, all seemingly posting a coherent message about documentation/installation etc. but soon switching to issues with a racial slur in the title. Such issues were posted in my project as well.
Apparently Codeberg has regularly been targeted by such vicious attacks from extreme right movements precisely because Codeberg took a stance against hate speech and racism.
https://blog.codeberg.org/we-stay-strong-against-hate-and-hatred.html

So, this is the first thing we ought to acknowledge: the hard work expanded by the Codeberg team in order to keep this platform clean. Thank you.

Having said that, what the OP proposes makes sense, if feasible and if someone has the time to implement it.

Yes. I appreciate Codeberg for fighting hard against these orchestrated attacks. We just saw a big number of accounts who each created hundreds of issues within hours, all seemingly posting a coherent message about documentation/installation etc. but soon switching to issues with a racial slur in the title. Such issues were posted in my project as well. Apparently Codeberg has regularly been targeted by such vicious attacks from extreme right movements precisely because Codeberg took a stance against hate speech and racism. https://blog.codeberg.org/we-stay-strong-against-hate-and-hatred.html So, this is the first thing we ought to acknowledge: the hard work expanded by the Codeberg team in order to keep this platform clean. Thank you. Having said that, what the OP proposes makes sense, if feasible and if someone has the time to implement it.

One kind of adjacent thing is that it feels very confusing to get the original notifications, think they're legitimate, go to the issue, and just get slapped with a "generic" this-never-existed-404 page. Maybe it would be viable to differentiate in the 404 page somehow (at least to the repo owner/contributors) that it was banned by moderation/anti-spam?

One kind of adjacent thing is that it feels very confusing to get the original notifications, think they're legitimate, go to the issue, and just get slapped with a "generic" this-never-existed-404 page. Maybe it would be viable to differentiate in the 404 page somehow (at least to the repo owner/contributors) that it was banned by moderation/anti-spam?

@natkr wrote in #1878 (comment):

Maybe it would be viable to differentiate in the 404 page somehow (at least to the repo owner/contributors) that it was banned by moderation/anti-spam?

Forgejo don't keep records if spam is removed, however if you look closely at the 404 page it already mentioned this:

The page you are trying to reach either does not exist, has been removed or you are not authorized to view it.

@natkr wrote in https://codeberg.org/Codeberg/Community/issues/1878#issuecomment-3932780: > Maybe it would be viable to differentiate in the 404 page somehow (at least to the repo owner/contributors) that it was banned by moderation/anti-spam? Forgejo don't keep records if spam is removed, however if you look closely at the 404 page it already mentioned this: > The page you are trying to reach either does not exist, **has been removed** or you are not authorized to view it.

My repositories have been spammed with nonsense issues as well. Somehow the contents of the texts sound like real bug reports at first, but if you look at the details and know the game, they don't make sense.

For reference, here's a fake bug report I received for Repixture (it's already deleted by Codeberg, I only know about it due to the e-mail notification):


BEGIN OF FAKE BUG REPORT


🚨 Issue Overview 🚨

Hey team! 🙋‍♂️ I'm having a MAJOR problem with the crafting system in Repixture! 😤 I just discovered that the Welder tool isn't listed in the crafting guide! 🤯 🤦‍♀️

📝 Steps to Reproduce 📝

  • Open the game 🌍
  • Check the crafting guide 📜 (I've attached a screenshot for reference! 📷 )
  • Search for "Welder" 🔍 (No results found! 😤 )

🤔 Expected Behavior 🤔

I expected to see the Welder listed as a craftable item! 🛠️ It’s so important for building! 🚧 I mean, how are we supposed to build without it?! 😩 🤷‍♂️

😞 Actual Behavior 😞

The crafting guide doesn’t show the Welder at all! 😱 This feels like a huge oversight! 📉 I thought I'd gone crazy, but I checked twice! 😵

🏷️ Additional Info 🏷️

  • Version : 3.17.2 📅
  • Platform : Luanti 5.8.0 🖥️

🆘 Urgent Fix Needed! 🆘

I really think this needs to be fixed ASAP! If you could add the Welder to the crafting guide, that would be SUPER helpful! 🙏 🔥 Please let me know if you need any more info from my side! 🚀

Thanks for your hard work on this game! 🎮 Keep it up! 💪 💖

P.S. I found this bug while trying to craft a boat! 🛶 And now I'm stuck paddling without a Welder! 😩 Let's fix this so everyone can boat happily! 😂


END OF FAKE BUG REPORT

The problem? My game doesn't have a welder, never had one. But the rest is correct: The version number, the platform, there is a crafting guide, there are boats (well, almost: there is a log boat and a raft). The excessive use of emojis also kinda gives it away, because it's rare for me to get issues with so many emojis. I assume this text was generated by a LLM and the README and game manual were used as input. I received multiple such nonsense issues with a similar writing style. Multiple accounts were used.

BUT! The important takeaway is, the spammers still lost. 😁 All nonsense issues I've received are already 404'ed, so good work by the moderation team!

My repositories have been spammed with nonsense issues as well. Somehow the contents of the texts sound like real bug reports at first, but if you look at the details and know the game, they don't make sense. For reference, here's a fake bug report I received for Repixture (it's already deleted by Codeberg, I only know about it due to the e-mail notification): ----- BEGIN OF FAKE BUG REPORT ----- > ------------------ > 🚨 Issue Overview 🚨 > ------------------ > > Hey team! 🙋‍♂️ I'm having a MAJOR problem with the crafting system in Repixture! 😤 I just discovered that the *Welder* tool isn't listed in the crafting guide! 🤯 🤦‍♀️ > > 📝 Steps to Reproduce 📝 > ---------------------- > > * Open the game 🌍 > * Check the crafting guide 📜 (I've attached a screenshot for reference! 📷 ) > * Search for "Welder" 🔍 (No results found! 😤 ) > > 🤔 Expected Behavior 🤔 > --------------------- > > I expected to see the Welder listed as a craftable item! 🛠️ It’s so important for building! 🚧 I mean, how are we supposed to build without it?! 😩 🤷‍♂️ > > 😞 Actual Behavior 😞 > ------------------- > > The crafting guide doesn’t show the Welder at all! 😱 This feels like a huge oversight! 📉 I thought I'd gone crazy, but I checked twice! 😵 > > 🏷️ Additional Info 🏷️ > --------------------- > > * *Version* : 3.17.2 📅 > * *Platform* : Luanti 5.8.0 🖥️ > > 🆘 Urgent Fix Needed! 🆘 > ---------------------- > > I really think this needs to be fixed ASAP! ⏰ If you could add the Welder to the crafting guide, that would be SUPER helpful! 🙏 🔥 Please let me know if you need any more info from my side! 🚀 > > Thanks for your hard work on this game! 🎮 Keep it up! 💪 💖 > > P.S. I found this bug while trying to craft a boat! 🛶 And now I'm stuck paddling without a Welder! 😩 Let's fix this so everyone can boat happily! 😂 ----- END OF FAKE BUG REPORT ----- The problem? My game doesn't have a welder, never had one. But the *rest* is correct: The version number, the platform, there is a crafting guide, there are boats (well, almost: there is a log boat and a raft). The excessive use of emojis also kinda gives it away, because it's rare for me to get issues with so many emojis. I assume this text was generated by a LLM and the README and game manual were used as input. I received multiple such nonsense issues with a similar writing style. Multiple accounts were used. BUT! The important takeaway is, the spammers still lost. 😁 All nonsense issues I've received are already 404'ed, so good work by the moderation team!

Yeah, I had a couple of these. I simply disabled the issue tracker on my project, since I don't use it anyway. But it's quite annoying.

I'm not sure what the answer is... maybe allow projects to forbid users whose accounts are less than a week old from creating issues? Or hide issues from everyone but project maintainers unless a project maintainer explicitly makes the issue publicly visible?

Yeah, I had a couple of these. I simply disabled the issue tracker on my project, since I don't use it anyway. But it's quite annoying. I'm not sure what the answer is... maybe allow projects to forbid users whose accounts are less than a week old from creating issues? Or hide issues from everyone but project maintainers unless a project maintainer explicitly makes the issue publicly visible?

2 important considerations:

  1. Attackers can easily adapt to any counter-measure. They base their attack plans on known defences, so it is hard to find a solution that is robust, durable and possibly non-intrusive and non-obstructive for bona fide users.

  2. Codeberg is a non-profit, and their service is based on Forgejo which is an open source software.... So, the only thing missing to implement the solution for 1) is a volunteer to do the work...

In all of this, the easy part is to complain about the slight disturbance and inconvenience that we all experienced from the most recent attack...

2 important considerations: 1) Attackers can easily adapt to any counter-measure. They base their attack plans on known defences, so it is hard to find a solution that is robust, durable and possibly non-intrusive and non-obstructive for bona fide users. 2) Codeberg is a non-profit, and their service is based on Forgejo which is an open source software.... So, the only thing missing to implement the solution for 1) is a volunteer to do the work... In all of this, the easy part is to complain about the slight disturbance and inconvenience that we all experienced from the most recent attack...

Yes, I understand, and I was not criticising Codeberg. I understand that it's a very, very difficult problem.

Yes, I understand, and I was not criticising Codeberg. I understand that it's a very, very difficult problem.

Hopefully resolved for now.

Hopefully resolved for now.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
7 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1878
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?