No, but it's not just falling over entirely that's the problem. APIs go down all the time so that's a case you'd hopefully handle gracefully. But when your proj

No, but it's not just falling over entirely that's the problem. APIs go down all the time so that's a case you'd hopefully handle gracefully. But when your project suddenly and silently produces an empty blank result, say. And you learn that's not some transient issue, that's how it is now. That's a huge breaking change for you. A non-breaking change, at least in the short-term, would be to continue providing the old data as is. Yes, the project might still be dead but how about showing people just an ounce of respect? This isn't rocket science, this is customer relations, and yet an established company like Strava still behaves this way. I appreciate you sharing this. Perhaps I am an idealist but it doesn't hurt to tell consumers that you are going to break the API contract you made with them. It's how I choose to treat the people I work with because I want to keep working with them. Supporting your old stuff is hard and frustrating when internally you've moved on, I get that, I do it too. Both as a consumer of free APIs like this and in my day job where there's obviously money involved too. But even with a free API like Strava's there is value for both sides, without that value at least one side wouldn't even be there. If you want to take advantage of that value in the long-term. there is an underlying agreement you don't screw each other over. If you do play these unprofessional games then don't expect people to be happy about it, don't expect them to be understanding, and don't expect them to work with you again. I'm not arguing against making changes if they need to made. I'm arguing against arrogant and/or lazy companies that screw people over when they implement their changes in this way. These companies can do better and so we should call them out on it.