27 ms·

Interestingly, a search for "retard" in code on GitHub yields over 200,000 results: https://github.com/search?q=retard&type=Code&utf8=%E2%9C%93 https://github.

by shawnps 11y ago

Interestingly, a search for "retard" in code on GitHub yields over 200,000 results: https://github.com/search?q=retard&type=Code&utf8=%E2%9C%93 https://github.com/search?q=retard&type=Code&utf8=%E2%9C%93 Not sure what made this particular case different.

barsonme 11y ago
Or, decidedly even more offensive: https://github.com/search?utf8=%E2%9C%93&q=nigger&type=Code&ref=searchresults https://github.com/search?utf8=%E2%9C%93&q=nigger&type=Code&...
- forthwall 11y ago
  Most of those are badwordlists.
  - barsonme 11y ago
    On the first couple pages, yeah. Skip 10+ pages and you get stuff like "nigger stole my bike" etc. As a side question, shouldn't it be fairly easy to flag those repositories and then sort through those who have it as an offensive word list and those who are just being derogatory?
austenallred 11y ago
Probably that someone complained
deleted 11y ago
[deleted]
EugeneOZ 11y ago
I don't understand why they don't filter it on upload stage ("push"). "git push" > "sorry, can't push because of words: [list of words here]". Is it more difficult than later disable whole repo because of one stupid joke?
- danielparks 11y ago
  Because you may need to put those words in a repo in a non-offensive context. For example, a list of "bad" words to look for.
  - EugeneOZ 11y ago
    I'm against censorship at all, but when humans are involved in process, it becomes much worse.
  - Cthulhu_ 11y ago
    You could work with hashed variants in that case; there might be performance benefits there, too.