I get the impression that Xert has a fundamental misunderstanding of the new picture here, but it could easily be me that is wrong too.
It could be a fundamental misunderstanding, or a purposeful interpretation to continue forward until Strava cares enough at which point it becomes an actual problem for them. >_>
I went out for a walk after dark during the spell in the UK where it had been overcast for a month and in sarcasm titled it the ‘sunniest part of the day’ I got back to AI complimenting on my brisk summers day walk; the only reason it was brisk was because it was freezing 
One thing that comes to mind is that the email Intervals.icu got explicitly said “your app has been identified as being in conflict” and perhaps the notice Xert got didn’t include that so they (correctly or not) feel they are safe.
Interesting, I just have to wonder how that determination is/was made?
It could simply be that they’re making assumptions and not applying this policy fairly or equally; Intervals.icu is just one person so they’re more comfortable telling David to kick rocks than they are telling Xert the same.
Or it could be that you have to fill in a form saying how you will use the data as part of your agreement with strava
Possible Strava is telling specific developers they can use data for their specific app even if it technically runs afoul of the language; various developers have said they have meetings scheduled to discuss how the update will impact them, so maybe those are Strava saying “business as usual.” The update could have been written very broadly to cover all possible future outcomes (IP lawyers gonna PI lawyer).
This is a shitty way to do it, esp giving only 30 days and no forewarning. But it does feel like Strava is trying to backpedal a bit, having recognized that actually implementing this will alienate their most loyal user base.
- If true, that seems another appropriate summary for how poorly Strava is handling all of this.
I feel like we are in for a new interpretation:
strava [Stray-vuh]
- Noun, Proper Noun
- app for recording and sharing fitness activities
- Noun, slang
- alternative for
- I thought I was going to do so well, but I ended up in a pile of Strava after my mistakes.
- alternative for
- Verb, slang
- screwing up a task in every way possible
- My buddy Strava’d that enduro run and ended up in the hospital for days.
- screwing up a task in every way possible
The alternative way forward for TR here…
“Er OK sorry all that AI talk was just the marketing department.”
I’m going to be petty, but I really wish Garmin, TR, activity source apps would add a clause specifically saying Strava cannot use data shared with it for AI purposes/ shared with other users.
We can the sit back and wait for Strava’s board to fire the idiots behind the policy change and crawl back to the broader community with a mea culpa apology
As a garmin, trainerroad and zwift user, i just don’t see any use case for Strava. I used have some sort of a soft spot for the data-hub with social benefits it was, but this has sealed it for me.
Read again, not users but apps and @davidtinker has shown his communication from strava. This will impact everyone that uses strava to sync data to some 3rd party coaching/ training service
Read the email he got from stava below
While I didn’t have this particular square on the Bingo card, I’m not surprised in the slightest by (yet another) dick move from Strava. It’s a bit rich that a company that built themselves almost entirely on data freely shared from other platforms would suddenly become the Data Soup Nazis, but well within recent (last 5 years) character.
As a Wahoo user and TR subscriber, I just learned today that the only way my outdoor rides were getting to TR was through Strava, and that there’s currently no way to bypass this soon-to-be closed portal. I want to extend a big “FU” to Strava for this policy change, with an extra emphasis on the “U” for the short notice and timing.
But I also have to take TR to task a little bit for relying on a company that clearly has ambitions (however misplaced) to become a competing training platform as a conduit for Wahoo data. I sure the hell hope the direct Wahoo integration is complete by the time spring outdoor riding season resumes!
I’ll have to take some blame, too, for just assuming everything would “just work” if I bought something as popular as a Wahoo. Had I researched it a bit more, I probably would have stuck with Garmin when I needed a new head unit last year.
Why, though? They relied on Strava as a conduit for data because they positioned themselves as that conduit, by making it more convenient to integrate with them than with multiple platforms and manufacturers with disparate APIs. If anything, until a few days ago integrating with Strava was the less risky choice, since Wahoo arguably has a bigger incentive than Strava to lock down their data, given that Systm is a direct competitor to TrainerRoad.
Yes. Like I said Strava aren’t bothered about us.
“If anything, until a few days ago integrating with Strava was the less risky choice, since Wahoo arguably has a bigger incentive than Strava to lock down their data, given that Systm is a direct competitor to TrainerRoad”
I’m going to have to disagree with you here. I think it would be suicidal for a device maker to block or otherwise significantly hinder the usefulness (via terms of service) the data they collect from general export to external platforms. There’s legal peril in specifically blocking individual companies from data, so it would be HIGHLY unlikely that Wahoo would target TR specifically. They could shape the TOU in such a way that they would essentially stop TR from using their supplied data, but that would also stop many others from doing so as well. Most critically, Strava. Show me a head unit or fitness watch aimed at enthusiast athletes that doesn’t mesh with Strava, and I’ll show you a device with minimal market potential.
Like it or not, Strava are still the goliath in this space. And they are probably correct in the assumption that they are in a strong enough position to expect that data be still be freely fed to them, but can choke the downstream users. The hardcore riders and runners who use outside training apps represent a small percentage of all Strava users. But there’s still a huge contingent of Strava users who are in the “casual” to “semi-serious” range. They want a place to collect their individual and aggregated workout data, and maybe do a low-level analysis of their fitness situation, but aren’t so hard core that they’re using an external coach or dedicated training platform. Strava does enough for them now, and is looking to become the option those people go to if/when they do decide they want train more deliberately in the future. Strava seem willing to anger the current hard core athletes on the platform if it means they can retain (and further monetize) athletes who grow into hard core athletes in the future.
Ugh, I had just recently figured out the magical dance to keep TR, Strava, Wahoo, and Apple Watch all in sync.
Its funny, I pay for Strava, mostly just because I understand their predicament; I’m there for most of their free features. The only subsriber feature I really use is the Fitness/Freshness chart, because I like to see how my total workload varies over time, which TR doesn’t have.
If Strava isn’t acting as my single source of truth for storing/sharing data with other platforms, I really have no real reason to be there.
Why? That’s exactly what Garmin does. The Garmin Connect API is not open, you can’t just sign up for access, you have to request it and they have zero obligation to grant you or anyone else access to it. And as stated in previous posts in this thread, they don’t push outside activities via their API, which is why Zwift activities pushed to Garmin Connect don’t end up in TrainerRoad. They haven’t even allowed new partners to push activities to Garmin Connect in years. Garmin seems to be doing fine.
They could shape the TOU in such a way that they would essentially stop TR from using their supplied data, but that would also stop many others from doing so as well.
That’s my point, that’s exactly what Strava did and there is nothing stopping Wahoo or Garmin from doing the same thing at any point in the future, so it’s not really fair to “take them to task” for making the decision to integrate with Strava years ago, when a) that streamlined the integration and b) it may have seemed like the safer choice at the time.
Well, Strava ended up being the one who effectively cut TR off. And it wasn’t an either/or choice. There was nothing stopping them from pursuing the Wahoo direct API as a contingency against this scenario. TR simply incorrectly calculated that it wasn’t a high priority. I’m not mad at TR, but am a little disappointed. Wahoo aren’t some fringe device brand. They left themselves exposed and got burned. Now my TR experience stands to be compromised.