A friend and I descended Latigo Cyn, caught our breath and had some nutrition at the bottom, then headed up. Apparently somewhere at the bottom, we triggered the segment start even though we were not moving. First off, that's bad segment design, should always start a tiny bit up the climb to avoid situations like these. But can't Strava deal with this intelligently by recognizing that there was zero progress at the segment start, and not begin the real timer until there is progress? Regards, Paul
