There's only a feature in github to forbid issues being created by "new accounts" which means if the account is older than 48 hours, it can still spam the shit out of your organization. And good luck trying to keep up with hundreds of accounts simultaneously spamming comments with racist and harrassment content. And this feature only exists for organizations, not for public repos owned by a person.
The only alternative is to make the github orga only accessible to triage members or maintainers, which would kind of defeat the point of issue tracking and bug reports.
Things would be so much easier if GitHub/GitLab/BitBucket had an automoderation bot that does this for you, even a simple blocklist of words or syllables would decrease most of the spam.
As most of the chans/spammers use lurking accounts that they reactivate for that purpose, they're very easy to identify. Their email addresses used in git are always from the same providers, and they always use the same kind of language, same kind of avatars, same kind of grammar and questions avoiding the main topic. So it's easy to spot them via a simple ML trained model (bert or tacotron models could easily classify this). Probably even a seq2seq model would be enough.
But yeah, guess this was just my two cents that GitHub has a moderation problem.
[1] https://github.com/tenacityteam/tenacity/issues/99#issuecomm...
- Author of the fork claiming that he recieved 70+ calls on his pinephone and jokingly said it didn't crash. [1]
- He deletes said tweet moments after someone asked him how anyone might've found his pinephone number despite it not being on his website or social media. [2]
- Then he says he doesn't have any proof becuse he had to wipe/reflash his phone due to his pinephone crashing (this directly contradicts his previous tweet). After being called out, he immediately deleted his HackerNews post. [3]
- The author was posting f-word and r-words on his github bio. [4]
sources:
[1] http://web.archive.org/web/20210706000825/https://twitter.co...
[2] https://news.ycombinator.com/item?id=27746263
Citing sources for specific claims does not mean that the overall conclusion is inherently true.
As issues are denied, a history of what type of spam or trolling is occurring is built up. That could presumably be aggregated and shared among the oss community, with concomitant spam arms race I guess.
If you want to raise the bar, I think a reputation system would be better.
I remember it working surprisingly well, especially browsing at 1 or higher, and I've never understood why no one has replicated it. 'Karma' systems must get better engagement.
Github issues is already a pretty high barrier (you need a github account to post).
I make software targeted at a technical audience, and only 10% of bugs are reported on Github. So by requiring Github you already lose 90% of potential bug reports.
(numbers in this comment are very rough estimates)
That's the goal.
Even that one you linked had someone from the community likely solve their problem and could be closed both for being irrelevant and for being solved. Several of the issues I checked were similar, probably bad reports but solved anyway.