Author Topic: [HAMR] 24th June - Teethgrinder Day 175 (Read 3232 times)

red marley · « **on:** 24 June, 2015, 06:09:45 am »

Early start for Steve today: 5:23am, heading NE. Whatever the problem was earlier this week, it doesn't appear to be affecting his riding now.

mcshroom · « **Reply #1 on:** 24 June, 2015, 06:18:13 am »

Allez Steve!

Wowbagger · « **Reply #2 on:** 24 June, 2015, 07:55:17 am »

The tracker failed to load for me just now. Is it just me?

clarion · « **Reply #3 on:** 24 June, 2015, 08:00:23 am »

Go Steve!

hatler · « **Reply #4 on:** 24 June, 2015, 08:07:37 am »

Tracker not working for me either.

red marley · « **Reply #5 on:** 24 June, 2015, 08:23:00 am »

It was working at 6am or so, but died for me sometime after 6:30.

I think this means that Steve's onboard SPOT tracker will get a little heavier this morning as the megabytes start backing up. #marginallosses

Oaky · « **Reply #6 on:** 24 June, 2015, 08:25:06 am »

Yep - trackleaders is now down - http://downforeveryoneorjustme.com/http://trackleaders.com/oneyeartimetrial15i.php?name=Steve_Abraham

It was working around 7:45 when I last looked.

Wowbagger · « **Reply #7 on:** 24 June, 2015, 08:29:33 am »

Quote from: jo on 24 June, 2015, 08:23:00 am

It was working at 6am or so, but died for me sometime after 6:30.

I think this means that Steve's onboard SPOT tracker will get a little heavier this morning as the megabytes start backing up. #marginallosses

Maybe he could put some of them on a USB stick and place it in his saddlebag, to keep the bike balanced.

Wowbagger · « **Reply #8 on:** 24 June, 2015, 08:57:20 am »

Tracker's back. 60 miles before 9am. A big one, I feel.

sg37409 · « **Reply #9 on:** 24 June, 2015, 02:11:19 pm »

Heres hoping ! He needs a lot of these now. Go Steve

Climberruss · « **Reply #10 on:** 24 June, 2015, 03:03:17 pm »

157 miles @ 9.5 hrs - he's going well today.

Climberruss · « **Reply #11 on:** 24 June, 2015, 05:22:44 pm »

180 miles in 12 hrs and still a long way from home. This is gonna be at least 250!

Go Steve!

Wowbagger · « **Reply #12 on:** 24 June, 2015, 05:25:21 pm »

He has been on some roads not previously used in his OYTT. I see he dropped into Necton Butchers. Is there something special about their sausages?

mcshroom · « **Reply #13 on:** 24 June, 2015, 06:21:27 pm »

187 miles on Trackleaders now and he's still the far side of Cambridge!

mcshroom · « **Reply #14 on:** 24 June, 2015, 10:48:49 pm »

Well he's home with 243 miles on the SPOT tracker. Strava still to come

Mothy · « **Reply #15 on:** 24 June, 2015, 10:51:04 pm »

256 according to his website

mcshroom · « **Reply #16 on:** 24 June, 2015, 10:52:15 pm »

Yep. Strava's now up

412km

Climberruss · « **Reply #17 on:** 25 June, 2015, 12:20:06 am »

Respect!

Ivo · « **Reply #18 on:** 25 June, 2015, 08:17:55 am »

It's flagged on Strava

Basil · « **Reply #19 on:** 25 June, 2015, 08:38:24 am »

Quote from: Ivo on 25 June, 2015, 08:17:55 am

It's flagged on Strava

mcshroom · « **Reply #20 on:** 25 June, 2015, 09:13:18 am »

Quote from: Ivo on 25 June, 2015, 08:17:55 am

It's flagged on Strava

I wish it would publicly show who flagged things on strava

BobScarle · « **Reply #21 on:** 25 June, 2015, 10:34:25 am »

If it's flagged on Strava does that mean that somebody, somewhere, for some reason, think it might be a bit iffy? Or is there more to it than that?

TimC · « **Reply #22 on:** 25 June, 2015, 10:41:33 am »

Could be that someone's hit the 'flag' button by accident? I hope that's all it is. Normally, stuff gets flagged for being dangerous or for cheating. For example, Alex Dowsett always self-flags rides done with motor-pacing. All it does, AFAIK, is remove that ride from segment leaderboards.

simonp · « **Reply #23 on:** 25 June, 2015, 11:05:07 am »

Quote from: TimC on 25 June, 2015, 10:41:33 am

Could be that someone's hit the 'flag' button by accident? I hope that's all it is. Normally, stuff gets flagged for being dangerous or for cheating. For example, Alex Dowsett always self-flags rides done with motor-pacing. All it does, AFAIK, is remove that ride from segment leaderboards.

It's quite hard to flag rides by accident since you have to supply a reason.

Climberruss · « **Reply #24 on:** 25 June, 2015, 12:11:43 pm »

Quote from: simonp on 25 June, 2015, 11:05:07 am

Quote from: TimC on 25 June, 2015, 10:41:33 am
Could be that someone's hit the 'flag' button by accident? I hope that's all it is. Normally, stuff gets flagged for being dangerous or for cheating. For example, Alex Dowsett always self-flags rides done with motor-pacing. All it does, AFAIK, is remove that ride from segment leaderboards.

It's quite hard to flag rides by accident since you have to supply a reason.

Possible malicious intent?

Author Topic: [HAMR] 24th June - Teethgrinder Day 175 (Read 3232 times)

red marley

red marley

simonp