Originally Posted by
canklecat
Yeah, you'd think there would be some automation. Maybe have Strava auto-generate "Can you confirm the accuracy of this segment?" to users posting unusually fast times.
But I see lots of stuff that was obviously the result of users not using auto-pause/resume, or failing to stop and finish a ride before getting in the car. I'd assumed everyone knew how to crop rides but a friend recently posted a question about cropping the end of a ride to eliminate the car ride home.
I'm new to Strava and noticed some absurd speeds (120 mi/h) on a segment of my commute that led to me discovering a lot of logged segments crossing the SR-520 bridge that predate the opening of the trail that made it even possible to ride across (outside of sanctioned events) -- everyone would have had to get on a bus or other vehicle. The fastest "riders" were hitting north of 50 mi/h across so I started flagging them, including the history of the bridge in the explanation field. Am I being over-zealous? It's not like I'm even close to KOM anything, so there's no skin in it for me, and some of these segments have been around for over a year so seems that no one else bothered.