Conversation
|
We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/75469600. |
|
@lcddave Any objection to this? This appears to only affect what words are used when the 'random-route' flag is passed when pushing an app. Cheers, |
There was a problem hiding this comment.
Soo, no more crapes? http://www.merriam-webster.com/dictionary/crape
|
It may actually be easier to find a published clean list of words instead of trying to fix this one. It'd be great if there were a clean list that was available in multiple languages. I wouldn't want anyone to attempt to translate any of this. |
|
If a list exists sure - but until then I think we should play it safe and remove the ones we can identify now. |
|
Makes sense, I wouldn't want someone to be surprised with a << horrible expletive >>.mybluemix.net |
|
@duglin Is there a specific goal you're trying to accomplish with these edits? I'm okay with taking them, but as @MarkKropf mentioned the list may still not be quite clean for some definition of "questionable." (I wasn't taking any action here because I was leaning toward retiring this implementation of random word anyway.) |
|
I guess my goal was to try to avoid someone getting upset at our choice of words. If that's achieved by the edits I've proposed or by removal of this particular random word algorithm then either is fine with me. But I do think that while the longer-term decision is made I think taking the easy steps of removing the ones I've proposed would be a good thing - some of those words could get us into quite a bit of trouble. |
|
This has piqued my curiosity. What kind of trouble can we get into with On Wednesday, July 23, 2014, Doug Davis notifications@github.com wrote:
|
|
Would you want to be the person to explain to your customer why CF is generating names that have, say, the N-word in it? |
|
Ah, didn't see the random-route part of the thread. On Wed, Jul 23, 2014 at 2:47 PM, Doug Davis notifications@github.com
|
|
Yes, this is not censoring route words, it just adds assurance that we will not create a random route with words you can't say on TV. I think that's reasonable and something we should bring in. We've been lucky thus far, let's not wait for the first incident to make this more important. |
|
Just found this: https://github.com/shutterstock/List-of-Dirty-Naughty-Obscene-and-Otherwise-Bad-Words/ It has a plaintext file for bad words in English (en) as well as 20 Still, a whitelist would be ideal. On Wed, Jul 23, 2014 at 3:34 PM, Mark Kropf notifications@github.com
|
|
It's still possible to cause offense. I started a project once that I felt On Wed, Jul 23, 2014 at 3:34 PM, Mark Kropf notifications@github.com
Rasheed Abdul-Aziz Level 2 Mobile: +1 (646) 462-5466 |
|
@duglin I apologize for not vetting the library as thoroughly as you, I'm appalled at what you've found. Definitely not the impression I want to create. Thanks for doing this. |
Merging this in, but it seems like a second pass might not be a terrible idea.
|
On a lighter note, while this isn't autocorrect, seems like the two areas share similar challenges: |
Merging this in, but it seems like a second pass might not be a terrible idea.
9 participants
No description provided.