Yes. (I mentioned that above)

CBenson wrote:Does waze expect this to be static finalized list? Or will we be adding an subtracting from the list based on user experience and abuse?

RIght now, it is a one-off. They already have an English list, but I am making sure it's up-to-date.

CBenson wrote:Is US English available to use worldwide? If so it seems a bit extreme to have things like africa, african, arab and nigerian on the list.

This is country/language-specific, so UK English has a different list. Not sure why a road report would ever need to use those words. Could you expand on how these could be validly used without being a slur?

CBenson wrote:Is this list for use only for user reports (including map chat) all for all of waze? In other words, I suppose we could ban liquor and lingerie from reports, but seem unwise to not use the term in store descriptions.

Anything under the Reports menu only (chat, accident, hazard, policy, closure, etc.)

CBenson wrote:Do we know what happens when someone uses a word on the list. Do we get a warning of some kind?

They are replaced by another character like an asterisk or something else. Can't remember right now.

CBenson wrote:Things on the list that seem to me that they might be more commonly used in the waze context for legitimate reports than in another context include backdoor, backseat, bi, black, burn, color, colored, crash, escort, flasher, gun, harder, knife, period, rearend, remains, shoot, shooting, and suicide.

I cam see these being ok, but no need for others: burn, crash, harder, rearend, remains.

The list is also word-specific, so will not search out sub-strings of words. That makes it easier to fool the filter, but we could also use wildcards for non-letter words. So, _-ASS-_ might make it in right now but classic would be allowed too. If we wildcard non-letter characters then 'classic' would still be allowed but '=asshole=' could get filtered.

The only use for this list that I am aware of is for user manually entered text which would appear in the app to someone else. So hazards, police, chat, etc.

The reason I posted this list is to have more eyes on it to remove words which are useful within the waze app. I know there are lots of words in the list which need to be removed.

Does waze expect this to be static finalized list? Or will we be adding an subtracting from the list based on user experience and abuse?

Is US English available to use worldwide? If so it seems a bit extreme to have things like africa, african, arab and nigerian on the list.

Is this list for use only for user reports (including map chat) all for all of waze? In other words, I suppose we could ban liquor and lingerie from reports, but seem unwise to not use the term in store descriptions.

I always wonder whether systems like this seem to me to do more harm than good. I understand we don't want a bunch of extraneous offensive reports and map chats. But on the other hand it will be a problem when every report is blocked when the traffic jam is caused by a bunch of naked people on the side road protesting the use of fur. If there is a sniper on the loose, should we really pretend that not talking about it make the situation better?

There are many words that I could see using in report, but could use something else. Do we know what happens when someone uses a word on the list. Do we get a warning of some kind?

Things on the list that seem to me that they might be more commonly used in the waze context for legitimate reports than in another context include backdoor, backseat, bi, black, burn, color, colored, crash, escort, flasher, gun, harder, knife, period, rearend, remains, shoot, shooting, and suicide.

Should the list include variations with special characters?

AlanOfTheBerg wrote:Only delete something if it really is not a "bad" word and/or also has no use within the context of App-based reports which appear to other users. Like "tramp" isn't really a bad word, but could that words be used validly within the context of a Waze road report or comment on a report or closure?

Well, what about "squaw"? It's definitely potentially offensive, but I also know for a fact that there are places in the USA with that word in their names.

The list is absurd. "Breast" and "cancer" are on it. We had pins ALL OVER THE MAP a couple months ago showing breast cancer treatment centers. Come on.

"Accident in front of the African restaurant." "Police hiding out in liquor store parking lot."

AlanOfTheBerg wrote:

CBenson wrote:Things on the list that seem to me that they might be more commonly used in the waze context for legitimate reports than in another context include backdoor, backseat, bi, black, burn, color, colored, crash, escort, flasher, gun, harder, knife, period, rearend, remains, shoot, shooting, and suicide.

I cam see these being ok, but no need for others: burn, crash, harder, rearend, remains.

"Remains"?! Seriously?! "Remains" is not offensive even if it is used to mean "dead body". It shouldn't even matter that "traffic remains backed up". Can we really not imagine why "crash" or "rearend" or "harder" would be in a report? "Bad crash ahead", "Car got rearended by truck", "Eisenhower Tunnel closed, you can take Loveland Pass which is a harder drive or you can wait it out"... I could go on.

What would you think if it said "Bad ***** ahead" or "Traffic ******* backed up"? Fill in the blank with something actually offensive, probably.

Hell, Michigan
Gaylord, Michigan

This has a chance to interfere with UR's.

Hell, Michigan is a extremely popular tourist destination. Gaylord is a prominent city on the trip anywhere north, as well as being home to many 4-wheeling trails. Making it very well traveled as well.


How strict is this going to be once in effect?

CBenson wrote:Is US English available to use worldwide? If so it seems a bit extreme to have things like africa, african, arab and nigerian on the list.

Whether limited to N/A or not, how are those words at all offensive? It is the context that makes them potentially offensive and only if someone is using them to attempt to get around the censors.
"Authentic African Cuisine" is a perfectly acceptable entry for a places update.

I always wonder whether systems like this seem to me to do more harm than good. I understand we don't want a bunch of extraneous offensive reports and map chats. But on the other hand it will be a problem when every report is blocked when the traffic jam is caused by a bunch of naked people on the side road protesting the use of fur. If there is a sniper on the loose, should we really pretend that not talking about it make the situation better?

Bingo.
A motorcycle forum that I used to participate on started to get VERY strict when they were attempting to "clean it up" (bikers? ) in preparation for sale of the domain and the sponsoring business.
They activated "string-specific" censure rather than the more common "word" specific censure.
They did this because people found they could bypass the censors by simply *framing* a word.
Of course, this lead to the problem of my motorcycle, a Vulcan 1600 Classic, appearing to the forum users as a Vulcan 1600 Cl***ic. "Wristwatch" was similarly censored, and we began referring to purchasing jackets and boots at "Male Genitalia's Sporting Goods" since "Dick's" was also blocked.

It took 6 months for the moderators to get the owner to see the stupidity and impossibility of making anything online 100% G-rated... the best you can hope for is PG-13.