Running

Made me wonder whether there is something going on with the gps round the emirates, or whether as it's a circle, the gps is triangulating and constantly cutting corners and hence giving a quicker time....

It's the opposite, it gets terrible GPS lock and thinks you've run further. Instead of running 100m down a road in a straight line it thinks you've jinked 10 or so yards off to the side, then 10 yards off to the other side and all of those inaccuracies build up.

The GPS lock doesn't affect the time, as that should be static, but if Strava thinks you've gone further than you have in a specific segment of time then it'll think you've gone faster.

In open country my Garmin Forerunner 935 is very accurate, I can even pick out where I've veered into the road to give people more than 2m distance. Running into work (SE1) it always goes loopy round the back of St Thomas' Hospital and that's before I get to the underpass below Westminster bridge.

The other think that people are doing on Strava now is a pisstake of the #RossBarkley5k.

Strava reports/displays moving time for a run, so people are going out and running 5k but doing it as sprints and rests, but the resting time doesn't count. So people are smashing out PB's all over the place (someone did a 12 minute 5k) but the elapsed time is way longer (some over an hour). Also some are doing them down big hills and pausing the activity while they jog back up and recover, then smash it down the hill again.

Just beware what you see on Strava's "Moving time", always look at "Elapsed time" or the pace graph to see if there are lots of gaps.