I mention this because it’s news to me, but some time in the past year Strava seems to have changed its handling of paused distance.
For example, if you record a ride to the local train station, then pause the GPS for the train ride, then unpause at the other station to continue the ride in the mountains, Strava will draw a straight line connecting both stations on the map, but not count the length of that line towards the total distance. This is just like RideWithGPS now.
Previously, Strava was counting that distance. The only way you could get a truthful count of your actual cycled distance was to record rides to and from stations on courses involving a rinko as separate activities. This also means that if you don’t use auto-pause, if you manually pause the GPS at a conbini, then forget to unpause after the break until several km down the road, Strava would previously count at least a linear approximation of the “forgotten” distance. Now, it will hold you responsible for the pause and give you zero.
Perhaps related to that, I am also finding that distance inside tunnels on bikes without a wheel speed sensor is no longer counted by Strava, which effectively treats it as if you had paused the recording for the length of the tunnel (while there was no satellite reception). Previously, the distance total of my GPS did not count the tunnels, but once I uploaded to the Strava website, the activity shown online would include the distance inside tunnels as it filled in the gap in the data, same as it did for the train ride.
As you can see, this change is a mixed blessing, with both advantages and disadvantages. I think on balance, the ability to use multi-mode transport without having to break up the course into multiple recordings is a winner. I wish Strava would still fill in the tunnels gaps in the data (when the pause button was never touched), but that’s a minor irritation compared to the clear benefits on train and ferry rides.