mapcat wrote:deeggo wrote:I would like to propose a smaller number of points for just confirming prices already put in. I fear people will just confirm prices of every station they pass, for gaining points.
That's not fair to the person who pulls into the station to add prices, and then sees that someone else got them first.
They're only worth 8 points anyway. Hardly an incentive to cheat.
mapcat wrote:Nacron wrote:The top two ranked people in Hawaii weekly have probably 90% of their points from drive by confirmation of gas prices, almost all the time the prices are "confirmed" by them and are wrong.
Report them to support. Note the stations, time you saw the bad prices, and what the correct prices were. How many points are they getting by doing this?
FWIW, nobody's reporting prices around me (besides "3rd party") and the prices are wrong here too.
pvaladares wrote:zabb wrote:We have troubles in Italy to insert the prices with iOs (iPhone and iPad).
It doesn't see the numbers after the point (.)
If you type 1.879, it takes 1.000
I am using latest Android beta client (220.127.116.11) and I just have to enter the 4 digits. No need to enter "." or ","
In my client it automatically formats the price.
Note: The current version has a bug (before editing prices they have "," and after edition they have ".")
pvaladares wrote:Bruno3589 wrote:Hi, I have problems too when trying to insert gas pricing in Italy with the Android app version.
When I am near or into the gas station landmark and I try to update gas prices, I get an error telling me that GPS is unreachable, even though it's not true (GPS is active, has signal, and Waze is using it to navigate).
I got the same error with both Waze 18.104.22.168 stable and 22.214.171.124 Beta, so I can't figure out what the problem is (I also tried clearing the cache, which did not help).
True. Today I had the same problem while updating most of gas stations in my way (maybe some anti-spam feature?).
Below I attached 2 examples
1 - Real GPS position
2 - Gas station
CBenson wrote:Twister_UK wrote: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.
This is a US station. The US stations can't be deleted in WME.
Twister_UK wrote: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.
Users browsing this forum: Google [Bot], wolfsbane2k