4 ms·
If it was the bad words/slurs, could that have been resolved by hiding them behind some basic string manipulation (ex. a caesar cipher)? I can see how GitHub wo
by compscistd 6y ago
If it was the bad words/slurs, could that have been resolved by hiding them behind some basic string manipulation (ex. a caesar cipher)? I can see how GitHub wouldn't want a public repo to have objectionable words, but can't imagine the harm from obfuscating stored copy.
- yellowapple 6y ago> I can see how GitHub wouldn't want a public repo to have objectionable words I can't. Does GitHub really have nothing better to do than to play nanny cop because I used a naughty word in my code? Are brainfuck interpreters now off-limits? How about drivers for teledildonics hardware? Or libraries specifically for detecting and filtering swear words? Or maybe I just want to vent a bit in a comment every once in awhile because of some annoyance with the language or target platform or problem to be solved? Fuck that and the horse it rode in on. We're all adults here (well, or possibly teenagers, but let's face it: they've probably already heard much worse at school). Not that this seems like the real reason why SS13 got nuked anyway; if GitHub really has some kind of anti-profanity rule, they're doing a real bang-up job of consistently enforcing it: https://github.com/search?q=shit https://github.com/search?q=shit / https://github.com/search?q=piss https://github.com/search?q=piss / https://github.com/search?q=fuck https://github.com/search?q=fuck / https://github.com/search?q=cunt https://github.com/search?q=cunt / https://github.com/search?q=cocksucker https://github.com/search?q=cocksucker / https://github.com/search?q=motherfucker https://github.com/search?q=motherfucker / https://github.com/search?q=tits https://github.com/search?q=tits
- MrStonedOne 6y agoWe named our meatballs a old british name. This was why we got nuked. If only we knew that 4 days ago when we first got banned, and not, well, 4 days later. The issue is github works by report only. You can do what ever you want in a github repo, but if you make a video game on github, and ban the wrong person, they can just go through your repo and look for ToS violations to troll you. We are literally removing the in game chat word filter for the n word out of fear it could be used to git us banned again by somebody else mad their buggy pr got rejected or their character got banned in game for breaking the server rules
- dijit 6y agoBlisteringly arrogant of a US company to police the language of another natively english speaking country. This is not the Scunthorpe problem, this is a culture one.
- judemelancon 6y agoIs the image, purportedly of a search of the codebase, in this post falsified? https://tgstation13.org/phpBB/viewtopic.php?f=2&t=26318#p554873 https://tgstation13.org/phpBB/viewtopic.php?f=2&t=26318#p554...
- yellowapple 6y agohttps://github.com/search?q=faggot https://github.com/search?q=faggot And taking this to its logical conclusion https://github.com/search?q=nigger https://github.com/search?q=nigger (And "kudos", I guess, to https://github.com/Zveu/NiggerFaggot https://github.com/Zveu/NiggerFaggot for managing to pop up in both) If using a naughty word is indeed a ToS violation, GitHub is rather arbitrary in its enforcement thereof. Like, is a Microsoft-owned corporation and the hub for the vast majority of FOSS development nowadays really unable to run its own search function and detect blatant racial and orientational slurs? Or maybe they banned their own profanity filter, lol
- deleted 6y ago[deleted]
- tjpnz 6y agoIf that's official GitHub policy it's both unworkable and exceedingly ignorant of how people use the English language outside of the US. GitHub should have no business telling people how to write their source files.