github-starred/awesome-sindresorhus
2
0
Fork 0
mirror of https://github.com/sindresorhus/awesome.git synced 2026-07-22 05:16:31 -05:00
Code Issues 1.7k Packages Projects Releases Wiki Activity

Spam comments stay on the project for pretty long #353

New Issue
Open
opened 2025-11-06 15:13:26 -06:00 by GiteaMirror · 13 comments
GiteaMirror commented 2025-11-06 15:13:26 -06:00
Owner
Copy Link
Copy Source

Originally created by @Mo-way on GitHub (Jul 13, 2025).

Currently, there are a lot of non-sense and spam comments in the PRs and Issues. For example:

  • Incubate issue is full of them.
  • The oldest one is over half a year old.
  • Table of content issue has them as well
  • Web assmebly PR also has a bunch of spam comments.
  • This very post collects them as well, ironically (At least I cannot imagine how Hhhhhyy is advancing the discussion)

Questions to anyone interested in the matter:

  • Is this just a temporary thing, because maintainers are currently pretty busy with their private lives?
  • Are there any other solutions to get rid of them (the spammers, not the maintainers)?
  • Personally, I think it's annoying, unprofessional and worth a little effort to get rid of. What do others think?

Ideas:
AFAICT, @sindresorhus is lifting the whole weight alone at the moment.
Reading Github's guide on disruptive comments it says that write access or an organization is needed to moderate comments.
Maybe there is some person, @sindresorhus trusts enough and who has some time on their hands.

Alternatively, we could try to get obvious Spam reported. I tried with GitHub, but didn't seem to work. Maybe it works if more people report the same comment. Or, maybe it's an option to notify maintainers somehow.

Just some ideas, curious for feedback.

Originally created by @Mo-way on GitHub (Jul 13, 2025). Currently, there are a lot of non-sense and spam comments in the PRs and Issues. For example: - [Incubate](https://github.com/sindresorhus/awesome/issues/2242) issue is full of them. - The [oldest one](https://github.com/sindresorhus/awesome/issues/2242#issuecomment-2552906489) is over half a year old. - Table of content [issue](https://github.com/sindresorhus/awesome/issues/1972) has them as well - [Web assmebly PR](https://github.com/sindresorhus/awesome/pull/3398) also has a bunch of spam comments. - This very post collects them as well, ironically (At least I cannot imagine how `Hhhhhyy` is advancing the discussion) Questions to anyone interested in the matter: - Is this just a temporary thing, because maintainers are currently pretty busy with their private lives? - Are there any other solutions to get rid of them (the spammers, not the maintainers)? - Personally, I think it's annoying, unprofessional and worth a little effort to get rid of. What do others think? Ideas: AFAICT, @sindresorhus is lifting the whole weight alone at the moment. Reading Github's guide on [disruptive comments](https://docs.github.com/en/communities/moderating-comments-and-conversations/managing-disruptive-comments) it says that write access or an organization is needed to moderate comments. Maybe there is some person, @sindresorhus trusts enough and who has some time on their hands. Alternatively, we could try to get obvious Spam reported. I tried with GitHub, but didn't seem to work. Maybe it works if more people report the same comment. Or, maybe it's an option to notify maintainers somehow. Just some ideas, curious for feedback.
GiteaMirror commented 2025-11-06 15:13:27 -06:00
Author
Owner
Copy Link
Copy Source

@qiunnley commented on GitHub (Jul 15, 2025):

Hhhhyy

@qiunnley commented on GitHub (Jul 15, 2025): Hhhhyy
GiteaMirror commented 2025-11-06 15:13:27 -06:00
Author
Owner
Copy Link
Copy Source

@shoury222 commented on GitHub (Jul 19, 2025):

You should google it, my bro 😎

@shoury222 commented on GitHub (Jul 19, 2025): You should google it, my bro 😎
GiteaMirror commented 2025-11-06 15:13:27 -06:00
Author
Owner
Copy Link
Copy Source

@PhillipBurtonIDoData commented on GitHub (Jul 30, 2025):

Maybe there should be a keyword to use, to indicate that an issue is Spam.

@PhillipBurtonIDoData commented on GitHub (Jul 30, 2025): Maybe there should be a keyword to use, to indicate that an issue is Spam.
GiteaMirror commented 2025-11-06 15:13:27 -06:00
Author
Owner
Copy Link
Copy Source

@NitinGangwal commented on GitHub (Aug 6, 2025):

I want to help you.

@NitinGangwal commented on GitHub (Aug 6, 2025): I want to help you.
GiteaMirror commented 2025-11-06 15:13:27 -06:00
Author
Owner
Copy Link
Copy Source

@Daddyyo22 commented on GitHub (Aug 14, 2025):

I can help out

@Daddyyo22 commented on GitHub (Aug 14, 2025): I can help out
GiteaMirror commented 2025-11-06 15:13:28 -06:00
Author
Owner
Copy Link
Copy Source

@soyam99-max commented on GitHub (Aug 18, 2025):

Scams are prohibited

@soyam99-max commented on GitHub (Aug 18, 2025): Scams are prohibited
GiteaMirror commented 2025-11-06 15:13:28 -06:00
Author
Owner
Copy Link
Copy Source

@Angel-Mathew007 commented on GitHub (Sep 4, 2025):

Hi!
I’m interested in contributing to this project and would like to help with this issue. Could you please provide some guidance on how best to proceed or assign it to me? I’m excited to contribute and learn.

Thank you!

@Angel-Mathew007 commented on GitHub (Sep 4, 2025): Hi! I’m interested in contributing to this project and would like to help with this issue. Could you please provide some guidance on how best to proceed or assign it to me? I’m excited to contribute and learn. Thank you!
GiteaMirror commented 2025-11-06 15:13:28 -06:00
Author
Owner
Copy Link
Copy Source

@Mo-way commented on GitHub (Sep 4, 2025):

Hi @Angel-Mathew007 Why this project specifically? The maintainer is fairly busy & I have no idea how you can help. Feel free to come up with your own ideas.

@Mo-way commented on GitHub (Sep 4, 2025): Hi @Angel-Mathew007 Why this project specifically? The maintainer is fairly busy & I have no idea how you can help. Feel free to come up with your own ideas.
GiteaMirror commented 2025-11-06 15:13:28 -06:00
Author
Owner
Copy Link
Copy Source

@Shahzad232 commented on GitHub (Sep 4, 2025):

Maybe Scams

@Shahzad232 commented on GitHub (Sep 4, 2025): Maybe Scams
GiteaMirror commented 2025-11-06 15:13:29 -06:00
Author
Owner
Copy Link
Copy Source

@adambhai commented on GitHub (Sep 8, 2025):

Testing

@adambhai commented on GitHub (Sep 8, 2025): Testing
GiteaMirror commented 2025-11-06 15:13:29 -06:00
Author
Owner
Copy Link
Copy Source

@prriyayadav commented on GitHub (Sep 14, 2025):

One small thing that might help with reducing spam is adding structured issue/PR templates.
When contributors have to fill in specific fields (like description, steps)it makes random comments less likely.

@prriyayadav commented on GitHub (Sep 14, 2025): One small thing that might help with reducing spam is adding structured issue/PR templates. When contributors have to fill in specific fields (like description, steps)it makes random comments less likely.
GiteaMirror commented 2025-11-06 15:13:29 -06:00
Author
Owner
Copy Link
Copy Source

@Mo-way commented on GitHub (Sep 17, 2025):

@prriyayadav Good idea! Are there templates for comments as well? From my observation, Spam issues are quickly closed, but comments (see the ones above) stay forever

@Mo-way commented on GitHub (Sep 17, 2025): @prriyayadav Good idea! Are there templates for comments as well? From my observation, Spam issues are quickly closed, but comments (see the ones above) stay forever
GiteaMirror commented 2025-11-06 15:13:29 -06:00
Author
Owner
Copy Link
Copy Source

@jodikalin67-png commented on GitHub (Sep 20, 2025):

Hi my account are way messed up some one is using. Y accounts I need advice

@jodikalin67-png commented on GitHub (Sep 20, 2025): Hi my account are way messed up some one is using. Y accounts I need advice
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
help wanted
invalid
list request
pull-request
Mirrored from GitHub Pull Request
 question
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#353