-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inaproppriate words #23
Comments
Hi @tajtiattila , thanks for let me know, I already deleted the most obvious offensive words, if you have any other besides sucker and robbery please post it so I can filter it from the results. |
One can find many, and I suspect the selection of the right words might be the biggest challenge of this project. Words similar to one another might be a problem, too. Eg. there is COLOR and COLOUR, which are the same thing just with American vs British spelling. Some words that seems unacceptable to as an address (apart from those containing the F-word) after a quick search: ASSASSIN* There seem to be some non-words I've stumbled upon: FFFF So I wonder if the method to put together the original word list was appropriate in the first place. One could generate word lists from existing street names. Assuming they can appear on houses and road signs, those should be acceptable, but can refer to locations themselves, so then the list would contain many misleading names. |
"WRONG" . I got that as a first choice for my address. |
I tried the demo site and my location happens to have assigned an address like WHO SUCKER and WHO ROBBERY. I am certain nobody would want to have those words in his Xaddress (or any geocoded location). I quick search in en.csv and adj_en.csv shows there are many inaproppriate words.
The text was updated successfully, but these errors were encountered: