foxitrot wrote:Twister_UK wrote: 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...
... 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.
I understand the problem with flakey ghost copies of GS in the DB. But I think that these points-fanatics would not bother entering some guessed prices, if the fields were empty.
I don't quite share your optimism here - given the lengths some users will go to in collecting points at the expense of data integrity, I'm not sure having to make up a price (they'd only need to fake the price for one fuel type in order to "earn" their 8 points, making it even easier than the genuine user who goes to the trouble of correctly updating several fuel type prices to earn the same points) a handful of times a month would be much of a disincentive.
To be honest, given that it is only 8 points/station, and given that there aren't all that many ghost stations in the db, I don't think it's worth expending much effort on changing the behaviour of price entry/confirmation just to stop some users picking up a few extra points each day from ghost stations - better for the Waze programmers to concentrate on resolving the problem which is allowing these ghosts to remain in the db in the first place.