Yup, deleting the cookies worked in chrome, no more black window here. Did not mention it before, but I flushed my chrome-cache at the first signs of trouble because that was what helped last time...

[Edit]
Neither did anything to the performance. "Loading road images" takes forever, unworkable.

It is like those long winterevenings our great-grandparents knew. Time for handicrafts, reading a book or update the wiki.

Mail a request to support to replace the misspelled name in the database.

Read again, gettingthere. The poster Brshk1 is not the victim of some Auto-Capitalization-routine. Some editor before him misspelled a cityname.

Ssssst!

There is no practical other solution. Either WME allows you to use every possible miscapitalization of a cityname - or what? Changes the cityname for all streets in the city to the last variant used?

If it would be too much to handle for support they COULD formalize the procedure, like creating a form. I think it is not happening too often (yet).

deeggo wrote:

RallyChris wrote:My personal opinion, is that they have shifted into a higher gear on the money making goals. Take it for what it is worth.

What makes you think that? What examples did you see?

Waze stated in the MegaWazer Meet Up at Waze USA Headquarters in Palo Alto in January 2012 that they are looking into other ways to monetize Waze.

They can't provide a product for free forever without a way to generate income. Their investors are not giving away money, they want a return on their investment.

There is no insight into who has modified turn restrictions. We have asked Waze to add this visibility (at least for the last modified turn for a junction) but they have not.

petervdveen wrote: Since the last update (world server) the connected segments that got changed turn orange when changing a junction.
This changes the edit date and editor of the segments.

How do you know which of the two junctions connected to the segment have changed? How do you know that the junction and not the segment itself had been changed?

This is not a proper solution...