10th anniversary Cool things to note!

[caughtatwork]

By the end of 2000 there were around 250 active cachers in Australia and about 100 in NSW alone.

http://geocaching.com.au/stats/cachers/ ... ve_by_year
http://geocaching.com.au/stats/cachers/ ... ve_by_year

[rhinogeo]

I'm not sure how the numbers are calculated in the graph

I started geocaching on 25/10/2003 (registered on GC on 21/10/2003) so today it's 2546 days since I found my first cache. The graph say 1728 days

Even more curious since I'm c@w's geo-grandfather ... yet according to the graph he has been caching for 128 more days than me (I'd actually been caching for 210 days before Facitman sired c@w )

[caughtatwork]

That graph is GCA dude.
I found a GCA cache before you did.

This for combined GCA and GC.
http://geocaching.com.au/stats/cachers/ ... est_active

[Geodes]

That graph is GCA dude.
I found a GCA cache before you did.

This for combined GCA and GC.
http://geocaching.com.au/stats/cachers/ ... est_active

I think there are a few oddities, all the same. I think gahpee are the longest serving cachers, yet they're only 7th on the table.

I checked Zytheran and Calumphing_four - and their earliest logs are obviously a bit dodgy

[caughtatwork]

I just make the output, based on the input.
Whatever people want to log and do is fine by me (mostly, unless you annoy me, then I get all stabby )

[Facitman]

... before Facitman sired c@w )

Please gentlemen, some people are probably eating dinner

[Cheesy pigs]

can we get a "stabby" emoticon?

[caughtatwork]

[Richary]

This for combined GCA and GC.
http://geocaching.com.au/stats/cachers/ ... est_active

So the oldest finders found a cache on 13/6/1998? I find that a bit hard to believe. Something is screwy in the logs somewhere.

Or could the results be being skewed by something like the Bridgeclimb virtual that was around and they logged it for the date they did the climb? Which is fine but renders the graph somewhat meaningless.

I could start a log your date of birth virtual, at least that would get me back to 1964 but I wouldn't be the oldest finder for very long! yes I like stabby too

[caughtatwork]

http://geocaching.com.au/cache/gcwgnv
Look at the last log.

Same on the GC log.
http://www.geocaching.com/seek/log.aspx ... 53a52c85ea

Saturday, June 13, 1998
Go yell at the man who owns the cache to delete the spurious log

(I like stabby too much, he is the inside me trying to stab its way out).

[Zytheran]

That graph is GCA dude.
I found a GCA cache before you did.

This for combined GCA and GC.
http://geocaching.com.au/stats/cachers/ ... est_active

I think there are a few oddities, all the same. I think gahpee are the longest serving cachers, yet they're only 7th on the table.

I checked Zytheran and Calumphing_four - and their earliest logs are obviously a bit dodgy

Yep, if you did your math you'd notice the date works out to be Jan 1st 2000.
...I wonder what that could mean?

Is there anything special about this date?????

The reason there is this particular date is because Groundspeak in their infinite stupidity don't allow you to log caches early on Jan 1st as you can't select the new year, in this case 2010, until it is Jan 1st 2010 in the US of bloody A. (Remember kiddies , there is no world outside of the USA. Two years I checked, once inside the USA the rest of the world ceases to exist, it's true I tell ya.)
So for a first FTF in SA for 2010 I set the date back 10 years to reflect what century Groundspeak were living in.

When GCA scraped the log off the GC site ,or whatever they do, they grabbed this initial log, which was set to 2000 however when it was edited 12 hours later to reflect 2010 GCA has not picked up the change.

So there ya go, happy?

[Zytheran]

http://geocaching.com.au/cache/gcwgnv
Look at the last log.

Same on the GC log.
http://www.geocaching.com/seek/log.aspx ... 53a52c85ea

Saturday, June 13, 1998
Go yell at the man who owns the cache to delete the spurious log

(I like stabby too much, he is the inside me trying to stab its way out).

Yeah, lets get a lynch mob together, that'll teach 'em.
Rather than deleting the 'spurious log', how about just correct the date. It's obviously meant to be 2008 or 2009.

/pulls on flameproof suit
I have a much better idea I promote whenever I can, lets stone to death programmers with no concept of input parsing or software testing? Once word gets out this will instantly improve the software around the planet.
It always amazes me that we'll cut IT people soooo much slack for crap software (e.g Windows and Microsoft in general) and yet when users make mistakes we come down on them like the proverbial. It seems to give the impression that the typically programmer has no idea about other humans, what they do or how they behave? (GCA admins excepted..)

[caughtatwork]

http://geocaching.com.au/cache/gcwgnv
Look at the last log.

Same on the GC log.
http://www.geocaching.com/seek/log.aspx ... 53a52c85ea

Saturday, June 13, 1998
Go yell at the man who owns the cache to delete the spurious log

(I like stabby too much, he is the inside me trying to stab its way out).

Yeah, lets get a lynch mob together, that'll teach 'em.
Rather than deleting the 'spurious log', how about just correct the date. It's obviously meant to be 2008 or 2009.

/pulls on flameproof suit
I have a much better idea I promote whenever I can, lets stone to death programmers with no concept of input parsing or software testing? Once word gets out this will instantly improve the software around the planet.
It always amazes me that we'll cut IT people soooo much slack for crap software (e.g Windows and Microsoft in general) and yet when users make mistakes we come down on them like the proverbial. It seems to give the impression that the typically programmer has no idea about other humans, what they do or how they behave? (GCA admins excepted..)

Phew. You get to keep your posting privileges.
Your log has also now been fixed.

[CraigRat]

When GCA scraped the log off the GC site ,or whatever they do...

Just FYI, without revealing the mysteries of the feed, I'd just like to flag that we don't scrape.

Another thing we should probably explain is that once a log is in the system, we do NOT usually update it, so if cases like this occur, you'll need to flag it to one of us to fix. We do this as a security measure to stop people injecting 'blank' logs to wipe the data we have.

But we are more than happy to assist on occasions like this once the GC end has been mended.