To #NoBAFS is to Know BAFS?

[cvcalhoun]

First, the leaderboard can take a few hours to update.

Second, you can delete the extra ride from Strava, instead of just marking it #NOBAFS.

[josh]

I’ve been a horrible volunteer, but I believe that new activity data is collected pretty quickly (triggered by webhook events), and that a daily syncing of activities for each athlete is done to accommodate edits and things of that nature (and people fall into different buckets in terms of when this synchronization is scheduled).

[DismalScientist]

Back in the olden days, the cache of all rides, correct, discarded, edited, or whatever, was discarded every night and refreshed with presumably corrected rides. Wait until tomorrow to see whether everything is fixed.

(Hmm… this gives me an idea as to how I can mess with the standings this evening.:rolleyes:)

[LhasaCM]

@DismalScientist 175035 wrote:

Back in the olden days, the cache of all rides, correct, discarded, edited, or whatever, was discarded every night and refreshed with presumably corrected rides. Wait until tomorrow to see whether everything is fixed.

(Hmm… this gives me an idea as to how I can mess with the standings this evening.:rolleyes:)

Since the update is now done throughout the day (per hozn’s update on the backend migration and josh’s post above, every individual is sync’d once per day, but the people are split up into groups to reduce workload), and some updates happen realtime with the webhooks (but not all), the timing of all of that may mean that the outcome of your idea doesn’t meet your expectations. But you never know until you try!

(But yes – wait until tomorrow – or just delete the duplicate file once you’ve seen how the devices compared.)

[Author]

Posts