Points conflict

[foxitrot]

Yeah I tried that shortly after joining then I found http://bit.ly/WazePoints

Yes, I'm talking about exactly this table.
I was just thinking about the points before. After getting aware about the table, I've started to regularly multiply it with my Dashboard figures. And it never matched...

I admit that "adding street names" is an unknown variable, but I suspect I do not add that much street names to make my calculation match the results (and yes, I've tried to guess some sane numbers of added street names too).

[gettingthere]

From my observation, here is how this works:

* The server keeps track of your points and is the accurate source. These will show on your Dashboard and Scoreboard.
* The client also tracks points but does NOT sync with the server other than the initial sync when you install the Waze application. So if you frequently edit, get lots of editing points, but for whatever reason the server does not 'push' enough 750 point editing candies to your client - the client point ticker will fall behind and never catch up.

Recently my client ticker points were off by more than 100,000 points!

The workaround here is to remove the Waze application and re-install. This client will get the current point total again from the server - one time.

This is all mute though since Waze 3 does away with the client point ticker and this confusion. Just hang in there until Waze 3 is released and your problem will go away! Ignore the total on the points ticker in the meantime.

[gettingthere]

In my case, the points difference is a lot more than 50%. And the wazers' icons will probably keep their lower point amounts even if using Waze v.3 clients, unless the client would be capable of syncing them with the server (or constantly complaining about being hungry for candies )

The info that you get when you click on another Wazer's icon is fed from the server, not the Waze application running on the other Wazer's smartphone. Only the server points matter. Ignore the client points on the points ticker...

[hallmike]

Try this:

http://www.waze.com/wiki/index.php/FAQ#On_My_Dashboard_all_my_points_have_gone.2C_and_the_date_of_last_update_is_very_old._What.27s_wrong.3F

.

[hallmike]

Well if that's the case, it doesn't do a very good job of estimating because the total points on my phone are about 80,000 less than the points shown on the dashboard. Appears the estimation algorithm needs tweaking.

[RallyChris]

Also the points on the phone are approximate. The server is the master points keeper, and it updates as your drives are analyzed. That was originally designed to be about 1 day, but with popularity of the service, this sometimes is longer.

Once a day, the phone asks the server what it thinks your points are, and then approximates from there till the next refresh.

[Seasider]

The client servers are struggling to keep up with the main servers. Your dashboard is the only accurate (ish) record of your points.
My own client banner scoreboard is over 10k points behind the dashboard. It will eventually catch up tho

[xbassman]

Well if that's the case, it doesn't do a very good job of estimating because the total points on my phone are about 80,000 less than the points shown on the dashboard. Appears the estimation algorithm needs tweaking.

I thought I'd bring back this topic....

To reinforce what hallmike noted, Here's a screenshot:



My points were at 404k when this shot was taken.
From what I have observed the total displayed by the client does update, but never syncs with the real totals. (probably a separate database)

If a user was to tap on my wazer icon they would see 220k 4 stars. (I have seen the same from wazers in my area whose points I know to be different than shown)

The only thing displayed correctly here is the rank.