3 ms·

When 4/8chan came to raid the audacity fork I created, we also had huge problems getting rid of spammy issues. There's only a feature in github to forbid issue

When 4/8chan came to raid the audacity fork I created, we also had huge problems getting rid of spammy issues. 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.

deleted 5y ago
[deleted]
mahkoh 5y ago
Are you the guy that people from 4chan attempted to kill over the fork?[1] Do you know when the case will be going to court? [1] https://github.com/tenacityteam/tenacity/issues/99#issuecomment-875319084 https://github.com/tenacityteam/tenacity/issues/99#issuecomm...
- datenarsch 5y ago
  That whole story is debatable at best. Here's just some of the things that make you scratch your head and wonder how much of it is really true: - 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.com/cookiengineer/status/1412201646378131459 http://web.archive.org/web/20210706000825/https://twitter.co... [2] https://news.ycombinator.com/item?id=27746263 https://news.ycombinator.com/item?id=27746263 [3] https://postimg.cc/BPXX26W1 https://postimg.cc/BPXX26W1 [4] https://archive.is/ZqK2T https://archive.is/ZqK2T
  - deleted 5y ago
    [deleted]
  - cookiengineer 5y ago
    The only answer I have to you: I learned not to give a damn about trolls. Maybe start something useful with your life instead of claiming things that aren't true?
    - leesalminen 5y ago
      The parent poster provided sources for all of their claims. It’s unclear to me what they said that was untrue. Care to elaborate?
      - ViViDboarder 5y ago
        None of it really has to be untrue to not draw the same conclusions. It’s possible that the phone crashed after some time, it’s possible they deleted messages and gave up because, as the parent comment suggests, they decided not to feed trolls. Citing sources for specific claims does not mean that the overall conclusion is inherently true.
nefitty 5y ago
Auto-update and lock all issues with the text "Waiting for moderator approval", tag them with "approval queue". In a private repo for contributors, duplicate the issue with original text and relevant metadata. Approval in the private repo entails adding the "approved" tag and simply answers the question "Is this spam?". When that tag is applied, the original issue in the public repo is updated and unlocked. Any edits trigger a similar process, "Edit waiting for approval". 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.

deleted 5y ago

[deleted]

mahkoh 5y ago

Are you the guy that people from 4chan attempted to kill over the fork?[1] Do you know when the case will be going to court? [1] https://github.com/tenacityteam/tenacity/issues/99#issuecomment-875319084 https://github.com/tenacityteam/tenacity/issues/99#issuecomm...

datenarsch 5y ago
That whole story is debatable at best. Here's just some of the things that make you scratch your head and wonder how much of it is really true: - 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.com/cookiengineer/status/1412201646378131459 http://web.archive.org/web/20210706000825/https://twitter.co... [2] https://news.ycombinator.com/item?id=27746263 https://news.ycombinator.com/item?id=27746263 [3] https://postimg.cc/BPXX26W1 https://postimg.cc/BPXX26W1 [4] https://archive.is/ZqK2T https://archive.is/ZqK2T
- deleted 5y ago
  [deleted]
- cookiengineer 5y ago
  The only answer I have to you: I learned not to give a damn about trolls. Maybe start something useful with your life instead of claiming things that aren't true?
  - leesalminen 5y ago
    The parent poster provided sources for all of their claims. It’s unclear to me what they said that was untrue. Care to elaborate?
    - ViViDboarder 5y ago
      None of it really has to be untrue to not draw the same conclusions. It’s possible that the phone crashed after some time, it’s possible they deleted messages and gave up because, as the parent comment suggests, they decided not to feed trolls. Citing sources for specific claims does not mean that the overall conclusion is inherently true.

nefitty 5y ago

Auto-update and lock all issues with the text "Waiting for moderator approval", tag them with "approval queue". In a private repo for contributors, duplicate the issue with original text and relevant metadata. Approval in the private repo entails adding the "approved" tag and simply answers the question "Is this spam?". When that tag is applied, the original issue in the public repo is updated and unlocked. Any edits trigger a similar process, "Edit waiting for approval". 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.