Should slower riders be able to flag faster riders

The need is to automatically exclude dubious times regardless of the device that is supposedly being used.

It’s not right that racing is supposed to be nice and clean while normal riding is supposed to put up with a wild west of cheating and exploits. Too many folks chant “it’s not a race” in response to all things, be it late joins, complaints about folks with dodgy power figures, etc.

Random guess, but I wonder if maybe half of casual zwifters are neither cheating or exploiting, but just bought a bunch of equipment that Zwift said works. I’m guessing there’s a lot less intent to be cheating and exploiting than you think there is.

5 Likes

But that’s not being done, and likely won’t be done. So while we’re speculating on things, the speculation I was responding to was simply about taking machines that are known to be inaccurate regardless of rider intentions off the lists.

1 Like

Someone doing multiple laps of ADZ non-stop with every lap at far better than world-tour-pro times is not simply oblivious to the errors.

And it’s the same people every day, they are called out on it multiple times and I assume have been flagged numerous times. It’s not right that it’s up to users to flag clearly dubious performances, those should be automatically flagged:

  1. hide the user
  2. remove their times from leaderboards
  3. Send them detailed information automatically. This should detail what happened and what steps they can take next. Details like how to get reliable power, calibration of trainers, etc.

Not every user needs to be verified and have accurate data.
Many people just want to Zwift and do not race.
They don’t care if their power is wrong.
Even if they train, they just want to compare to yesterday.

All that is good.

Trying to get everyone accurate is impossible.

Zwift should make some things harder to do.

Someone with outlandish power but just wants to Zwift should be allowed to do so but give his bike a reverse TT trait
No one can draft him, he is blocked from leader boards, and he is not allowed to race or, if he races, his rider pulls over to the side of the road with 20 k to go.

If he can demonstrate he is legit, let him go.

If not, he can keep playing the game but never allow him to cross a finish line, group ride or race.
That will get the attention of the accidental abusers and encourage them to fix the issue.

1 Like

Those can both be correct.

Exclude them from the leaderboards when they are doing impossible performances.

And don’t allow them do give any draft or get draft - that prevents them from destroying group rides or robopacer groups. But they need to be aware of why that is happening.

1 Like

There are other ways to protect group rides, and inaccuracy doesn’t affect those, or pacer groups, more than plain old people with accurate trainers being jerks.

Expecting fair and honest performances is not “being jerks”. I don’t mean just inaccurate power data, I mean also deliberate things like impossibly low weights and impossibly fast times.

If something isn’t done soon it’s going to get worse. I don’t really care what trainer is being used, just that if the performance is beyond normally possible it should get automatically flagged.

Lots of people have asked for that and it’s not unreasonable. Making them out to be villains is not right.

You are completely misreading what I wrote. I was drawing a distinction between people with unintentionally inaccurate trainers who might affect a group ride, and people who try to ruin group rides by just being jerks.

“inaccuracy doesn’t affect those, or pacer groups, more than plain old people with accurate trainers being jerks.” Inaccurate trainers don’t affect group rides more than people with accurate trainers in those group rides who are riding like jerks.

Well I don’t race, only use zwift for training but I felt quite good with myself when I managed to grab the epic reverse kom and the grade jerseys…even if it was only for a short while. Inaccurate power numbers degrade many non racer’s experience too

4 Likes

Closing this thread now. It’s run its course.

5 Likes