cancel
Showing results for 
Search instead for 
Did you mean: 
anchskier
Denali
Status: Gathering Kudos

Activity flagging and the idea of community moderation works fairly well, but there are always ways to improve it.  Here are a few ideas to consider or where I feel the current system is lacking in some form:

1.) Reset people's ability to flag activities at midnight, local time.  Currently, it is set up to reset 24 hours after the last flag was applied, which means you are always guessing when you will be allowed to flag another activity the next day.  There is no indicator telling you whether or not you will be able to flag an activity until after you have gone through the entire process and try to submit it, only to find out that you are still temporarily blocked.  This is a big waste of time.  Just reset it at the same time every day so it is obvious.  Another idea is to have some type of counter showing how many flags you have remaining in a day and/or when they will reset.  A note when you apply a flag that states something like "You have 5 flags remaining today" and/or "Your flagging ability will reset at 8:00am EST on XX/XX/XXXX."

2.) Nominate or allow local ambassadors who have more liberal flagging limits or abilities.  These people can be ones who submit an application and can be vetting by the location of the bulk of their activities over the past X number of years.  This will greatly help to clean up segments if someone is willing AND ABLE to flag more than 5 or 10 activities at a time.  

3.) Have a graduated limit to flags per day.  The more active the person is on Strava, the more flags they are allowed.  New members only get maybe 3 or 5 as a limit, but long-standing members get up to 100 (or whatever number works best).  These limits can be reduced if it is shown that they are abusing the system, determined by a percentage of flags applied that get overruled or otherwise proven incorrect.

19 Comments
Dobby1990
Shkhara

Made a similar post https://communityhub.strava.com/t5/strava-features-chat/flagging-a-review/m-p/24331#M4011

Would be good for Strava to actually review the process

Igor_Alves
Mt. Kenya

Kinda late to this thread but let me tell you guys that best way to do it since strava seems to not care about making the flagging better. In my city like almost every other we have a big avenue that it's focused on physical sports and it's plagued with people on bikes recording their activities as running ones or just GPS glitches that they don't care to delete it from leader bords. Today i flagged 15 people out of a 400m running segment that had a time of 38 or minus seconds faster than the world record lol, but after the strava limited me I just went in my brother's account and finished the rest of the flagging because I always do a full explaining and It takes quite a while to flag everyone and it sucks to write a full paragraph just to know that you reached your limit and just lost your response that you spent like 5 minutes writing and explaining. 

TLDR: Just change accounts when you reach the limit and finish it

ARoger
Pico de Orizaba

Two examples of clear car activities done in the last 7 days. Any half-decent auto-flagging shuld have picked these up:

  1. https://www.strava.com/activities/10876486559/overview - Reached 103 km/h in a 3% slope
  2. https://www.strava.com/activities/10872557248/overview - Reached 89 km/h in a 3% slope

 

 

 

L_McLoskey
Shkhara

I HATE that so many KOMs on Strava are obviously done on eBikes or in cars, with speeds of 50, 60, 80mph, etc.
I saw two today with max speeds of 93 mph and 111 mph (🙄), and came across a user with a bunch of KOMs and Top-10 segments who states in his own description that he rides an eBike!! Strava should catch these automatically and delete them.
I don't have time or desire to sit around playing Policeman and flag every obviously BOGUS KOM and car/eBike ride I see.
I'm not a "KOM-chaser" or obsessed with stats, but this is annoying, invalidates the entire KOM and segment stat system, and turns people off. This has been a Strava problem for *years* now, and it seems pretty clear that they have NO interest whatsoever in implementing what should be an easy software fix. Grrrrrr.