[notacoward]

Dealing with fakers is one of the key problems for any service like Strava. I have a set of ten segments that I do around town, and I constantly see bike times posted as running. I think most are accidents (e.g. forgot to change the activity type on their watch) but I've noticed some folks who seem more deliberate about it. BTW it's really not hard to tell. I've even seen a couple of times that were people in their cars, but those were even more obviously accidents.

To their credit, Strava tends to be really good about taking down times once they're flagged. OTOH, one of my own runs got flagged once, and the weird thing is that it wasn't even a particularly good time or anomalous in any way. If somebody wants to erase one of my below-average runs from the record, I think I'm good with that. :D

[nradov]

The thing is that Strava doesn't even try to automatically flag activities that are obviously fake or cheating. Their developers just seem completely lazy or incompetent. Like it should be trivial to automatically flag any activity that is significantly faster than the world record for that distance.

[stereocodes]

> developers just seem completely lazy or incompetent

why? you really don't need to go down that road. Are you a developer yourself? because I'm sure you don't enjoy someone saying you're lazy because you haven't implemented a feature that some rando on the internet thinks you should. You must not be a developer because you can't possible think that this decision lands squarely on the shoulders of the dev team.

[kenned3]

I've had my GPS go haywire and tell me my average speed was 833km/h. Do you think it is unreasonable to assume strava should have flagged this?

Strava needs to take more ownership of the rampant cheating. It is costing them users, and causing the overall quality of the product to go downhill. I use to be a big strava fan, now the only thing i use it for is to benchmark myself as anything else isnt worthwhile given the rampant cheating that takes place.

[notacoward]

There are a few cases that are trivial, but there are a lot more that can be very difficult. I'm sure the devs err on the side of avoiding false positives, because that could really enrage a user.

[nradov]

The problem is that the Strava developers have been too lazy to even catch the most obvious cases where there is zero risk of false positives. Like if someone "runs" a mile in 3:25 on a flat segment, is that really possible? It would be absolutely trivial to automatically flag those cases, but they haven't bothered to even try.

[stereocodes]

again you call the devs lazy. you really need to sit back and think about what you say. There is nothing more apparent to me that you have no idea what you're talking about when you say that. Obviously you've never worked on a large team or in development at all. Strava probably doesn't think its worth it, and has absolutely nothing to do with the development team.

[nradov]

I have done development work on large software product teams. I know what I'm saying and stand by my comment.

[stereocodes]

so you're just a jerk. nice.