foxitrot wrote:Maybe the always-only-confirmed prices should be reset after the default timeout period (two weeks ATM) and need to be manually entered at least once in a while? (Could be inconvenient, if some prices really do not change, but it would solve this way of cheating.)
Given that this station is still showing up as a valid location for price updates, either it hasn't been removed from the map, or the flakey back-end implementation has kept a ghost copy of this station in the database after it's been deleted in WME. So even if the price data gets reset after x days of staying at the same values no matter how often those values are confimed, surely all the points-fanatics will just have to enter new prices every x days and then continue confirming them as at present until the next x day timeout, then enter new price again and continue...
The real problem here is that the client believes this station is still active - fix that problem (either by a local editor removing the station from WME, or by Waze fixing their databases to prevent deleted stations continuing to appear in the client) and the problem of points-fanatics being able to earn points by confirming non-existent prices would be resolved without any means for them to work around it in the client.
They could always start editing the map and adding fake stations along their daily routes, but once that activity has been detected (and if Waze is already aware of their previous fake-price-pointgrabbing, it should be easy for them to quickly pick up on any odd-looking editing behaviour) Waze simply slaps a permaban on their editing rights, or possibly even removes their ability to earn points for anything but still allowing them access to the client in "read-only" mode so that it still functions as a satnav but without exposing any of the functionality (hazard reporting etc.) that could be used to inject malicious data and screw things up for everyone else if the user takes affront to having their point grabbing activities curtailed.