cb82

From Jeremy's Facebook page - "It is moving day at Groundspeak. Time to pack up the red stapler."

I think it had more to do with the fact that any app made with Groundspeak's api will only allow access to 3 caches a day for basic members. By using the new api, carnero would effectively be writing an app for only premium members. He didn't agree with Groundspeak's motives, which ultimately resulted in him abandoning c:geo.

Get an android phone. My Evo does everything I could possibly want and more, plus it has a very accurate GPS. It puts the Iphone to shame.

agreed

I won't do any. Not unless they decide to do a massive overhaul on how they are set up.

My ideal site would be one where they put up a feedback link for our ideas, and then acted on those ideas instead of just adding junk nobody wanted in the first place....

:lol:

My opinion: Virtuals are fun and have a place in geocaching Challenges are just plain dumb and should never have been introduced

That's 550% more that the number of users it took to reinstate the Google Earth KML file. At the rate it was climbing, it would have been the number one request a long time ago. Unfortunately, Jeremy removed it less than an hour after it was created and left a message that more or less said "Too bad, deal with it".

I agree. The feedback site had a request to remove them and it received over 1100 votes in under an hour before it was removed by Jeremy. It is fairly obvious that user's are not happy with these changes.

AMEN I have to agree.

Are you trying to suggest that people will go to a site that has minimal support only a handful of caches (most dual listed) and lots of issues just because they dislike challenges. I'm not buying that. A lot of people are showing their dislike in many ways and I'm betting there will be some changes to challenges that require them to be tied to a location. Then all they have to do is make them archive after so many negative votes. People won't leave because they dislike challenges, they'll leave because the owner of this site obviously doesn't care about what it's user's want.

+1

Already 1,100 votes to get rid of challenges - and it just got shot down...

This.

I don't mind the avatars, but I really have to question why Groundspeak is spending time changing things that nobody had a problem with in the first place. The ability to update the coordinates of a puzzle that you have solved has been the top request on the feedback site for a long time, yet that is still "under review" and we get all these changes that nobody wanted in the first place. Sounds like a lot of wasted effort. If they put the feedback system in place to find out what we wanted, why aren't they acting on any of those things? Yes, they put in "challenges" in response to the "bring back virtuals" request, but somehow I don't think that's what the 3600 votes had in mind...

here

I used 3 votes for this feedback thread: http://feedback.geocaching.com/forums/75775-geocaching-com/suggestions/2170437-bring-log-date-back-please They already said they would change it back.

Other than the date issue, I like the changes to the logs, and OpinionNate has already agreed to revert them back to the old date style.

So which listings are caches then, and which ones aren't? Let me guess: if it says "virtual cache" or "earthcache" and if it counts towards your find count, then it is, otherwise it isn't. Right? I rest my case. Great. You two should switch to a private conversation from here then. I think this conversation has gone about as far as its going to anyways. Thanks for the update on the challenges, looking forward to trying them out.

So which listings are caches then, and which ones aren't? Let me guess: if it says "virtual cache" or "earthcache" and if it counts towards your find count, then it is, otherwise it isn't. Right? I rest my case. You are absolutely correct. Things that you log as finds on this site are indeed all caches (including virtuals and earthcaches).

Coordinates from a listing with no physical container can also be a cache. Not all listings are caches, but they can be. I am not arguing that the listing IS the cache in all situations. But neither is the container.

So I ask you again: what is it that makes a cache a cache? Why aren't benchmarks caches? They fulfill all your requirements (has a listing). I'll ask you again: Why aren't coffee mugs caches? The fulfill all your requirements (has a container).