Thanks for all the comments, everyone. It’s been interesting to hear people’s views on this. Seems like responses fit into a few categories:
It’s fine because it’s all data that I can see on my bike computer anyways.
That’s not true at all. Your bike computer tells you about your effort, not about the efforts of others or about data calculated by zwift, like your current draft benefit. I race in A and hadn’t really thought about the fact it may help sandbaggers, but that is pretty trivial to do with a bike computer or another app anyways.
It’s fine because I can already get that data through ZwiftPower.
This is closer to true but still not right afaik. The “live” data isn’t really all that live and it’s still only a subset of what is available with Sauce isn’t it? Is there a way to use ZP to see my current draft benefit at this exact moment? Honestly asking, I don’t know.
It’s fine because I can get the same data from a human DS.
This is a good point IMO. Someone using Sauce has similar advantages to someone with a DS who’s observing the race while on discord, especially if the most helpful feature is the visualization of groups on the road. They can tell you about the gaps, who is in the group, how hard they’re working, etc. From that perspective Sauce makes things more fair not less because if you don’t have a DS you don’t have to be totally in the dark. For races with a lot of people the built-in zwift UI makes it difficult to see wtf is going on sometimes.
It’s fine because the game is more fun this way and it may encourage Zwift to implement it themselves.
Fair enough. I agree with the part about it being more fun.
It’s fine unless it’s Grand Prix or some more serious league like ZRL.
This one’s interesting because it acknowledges that it is an advantage and might not always be in the spirit of competition. To me this is proof of why it would be better to have clear rules. ie: make an actual API and officially support it, or don’t.
It’s obviously cheating because it violates TOS and it’s generally an explicit or implicit rule that it’s cheating to violate the TOS for a racing benefit.
I haven’t combed through the terms of service so I don’t know for sure that this is true, but it doesn’t look like sauce uses a public or semi-public API it’s more of a hack that I doubt is authorized, and it does require creating a second account so my best guess would be that it is a TOS violation. However, it seems that the counterpoint to this is generally: ya but who cares. Earlier in the thread a Zwift staff member said that he didn’t see anything wrong with this and then the post was deleted. I think they just don’t care either… for now.
All third party tools that hook into the zwift data stream should be banned to make races more equal.
This would certainly make it more fair across different devices. Counterpoint to this is often “have you tried a bike change on Apple TV?”. IMO bike changes are kinda lame and it would be more interesting if you could not change bikes mid race. Two wrongs don’t make a right. That’s just me though. I think the broader point here is should the race organizer be able to control the terms of the race or not? If this was part of a proper API ecosystem then the race organizer could create a No HUD race and then none of the data would be available on the API and the 3rd party tool would get disabled because it has no data to work from.
Random other observations.
Almost everyone I’ve talked to is in favor of Sauce, but the people that already use it automatically seem defensive, like they know what they’re doing is borderline and they’re struggling to justify it to themselves .
Personally, I like it but at the moment I’m not using it because it seems like a lot of faff. Getting all setup and ready to go on my trainer already has too many steps as it is.