What Comes After Gczzzz?

[+WalruZ]

I'm just curious is all. Waypoint IDs seem to be getting used a quite a clip.

 

BTW, FWIW, everything is peachy. I'm a premium member using GSAK and CacheMate and life couldn't be better. Well, I could have more time to cache, but other than that, I'm happy. []

[+planetrobert]

gzzzzz maybe?

[Jeremy]

The end of the world.

 

512400 caches will exist at that point. Unless we change the way we generate them, it will just add another digit to the end to make 7 digits total.

[+planetrobert]

what about 6 digit gps's

[Jeremy]

I said "unless we change the way we generate them." We may reconsider the way we generate them before then. If not, you can use applications to convert the name into something your GPS can digest.

[+planetrobert]

I said "unless we change the way we generate them." We may reconsider the way we generate them before then. If not, you can use applications to convert the name into something your GPS can digest.

my bad, i somehow read that twice and missed it both times...

 

anyway... my pda accepts more characters and that would be a good excuse to get a NEW gps

[+Hemlock]

If not, you can use applications to convert the name into something your GPS can digest.

Applications can be designed to drop the initial "G" or "C" or both.

[+Chaz]

Well then what comes after zzzzzz?

[+Renegade Knight]

Well then what comes after zzzzzz?

zzzzzz1

[Jeremy]

Well then what comes after zzzzzz?

Breakfast?

[+fly46]

Well then what comes after zzzzzz?

Breakfast?

LOL.

 

I'm sure that adding a number will be fine...

It was the last few times it was done.

[+Boo & Kitty]

While we're on the subject of limited cache numbers...

 

Are certain strings weeded out? This one is tame:gcHECK. Perhaps some others would be rather amusing.

[+G'n,G]

Well then what comes after zzzzzz?

Breakfast?

LOL.

 

I'm sure that adding a number will be fine...

It was the last few times it was done.

Until the server crashes from too much info!

[+Camo-crazed]

this is not really on topic but it is amazing how much interesting stuff you can find by typing in random wp #s, I just found a cache that had been archived that was 0.12 K from my house.

[+cachew nut]

The end of the world.

 

512400 caches will exist at that point. Unless we change the way we generate them, it will just add another digit to the end to make 7 digits total.

I think it might be better to add another digit to the front rather than to the end, and if the "GC" stays in place, then the new digit should come immediately after the "GC".

[Jeremy]

I think it might be better to add another digit to the front rather than to the end, and if the "GC" stays in place, then the new digit should come immediately after the "GC".

I'm missing the explanation as to why this is preferable. Adding a digit my way or your way both create unique waypoint names.

[+Mopar]

I think it might be better to add another digit to the front rather than to the end, and if the "GC" stays in place, then the new digit should come immediately after the "GC".

I'm missing the explanation as to why this is preferable.

Because it's the exact opposite of what you said?

[CoyoteRed]

Is there going to be a pool as to when the next rollover occurs?

 

Fizzy? Care to take a stab at a prediction?

[ju66l3r]

Is there going to be a pool as to when the next rollover occurs?

I'm going to bet on 6 AM tomorrow...when Mopar rolls over and makes Jeremy breakfast.

[+fizzymagic]

Fizzy? Care to take a stab at a prediction?

I recently made a prediction here.

 

It was for June 2007. It could be off a couple monthe either way. Not as far into the future as I would like.

[Jeremy]

I'm going to bet on 6 AM tomorrow...when Mopar rolls over and makes Jeremy breakfast.

My tolerance about personal attacks is at zero lately. see you in 7 days, ju66l3r

[+cachew nut]

I think it might be better to add another digit to the front rather than to the end, and if the "GC" stays in place, then the new digit should come immediately after the "GC".

I'm missing the explanation as to why this is preferable. Adding a digit my way or your way both create unique waypoint names.

Because your way is illogical. It would be similar to 99 + 1 = 990.

 

The waypoint IDs may no longer be used to determine the order in which the caches were placed, if someone should choose to try to determine historical data this way.

 

The question was what happens after GCzzzz and you replied add a 7th digit to the end. So now you have GCzzzz0. Very quickly you would reach GCzzzzz and that would require to start changing some of the previous digits downward. Once you did this, the following caches would appear to have been placed earlier than the ones from when you first introduced the 7th digit to the end.

[+cachew nut]

I think it might be better to add another digit to the front rather than to the end, and if the "GC" stays in place, then the new digit should come immediately after the "GC".

I'm missing the explanation as to why this is preferable. Adding a digit my way or your way both create unique waypoint names.

Just so you don't think I'm ignoring you, I did post an explanation yesterday, but my posts are being screened and I guess that one wasn't allowed. Maybe other viewpoints will no longer be allowed? Anyway, if you have a way to look at my post you will find your explanation there. I was kind of hoping it would be posted so that I don't end up looking stupid by others thinking that I could not provide an explanation. Have a nice day.