Corfman Clan

Hide a new cache in the same location and dedicate it to previous cache's owner and cite the above in the description.

That's a recent improvement to the cache submission process. There is no longer a way to set a default country and state.

Ya know, this whole discussion may become moot tomorrow. I imagine the option was dropped because the whole page is about to be redone and it "just doesn't matter." I'm on the edge of my seat with excitement!

My most favorite cache is a Wherigo, The Maze. It's a bit different than the standard tour cartridge. It gets fun logs but not as many visitors as I would like. Hopefully now that it's cooling off It'll get some more visits.

Just grab the bottom down corner and enlarge the text field. Hans Whether one is able to do that or not is browser dependent. At any rate, I agree, the field should be larger to start with. It probably should be above the forum signature too.

Before it was in a nice spot in the upper right. As far as I can tell, there's no way to add an image there.

I really miss having a profile picture. I don't consider the avatar a profile picture.

I used it all the time and I live in Arizona, a state that currently has over 29,000 caches. That's only a couple thousand less than Washington State.

The only thing I had filled out was the state. Apparently the link did not need my street or town. Now in the future when you take all this away, where are you going to get the state for the cache listing? Or will the cache listings no longer have the state? Or will we have a bunch of listings with the state blank? That was my same question here. My guess is that Groundspeak will want to initialize the state/country for new caches and it sure seems to me that that same mechanism could be used to get the list newest in <state> list.

Just curious what data are going to be used to populate the state/country for a new cache someone creates and why wouldn't that be used for the newest cache link?

From the explanation: I'm sorry, but that doesn't even begin to make sense to me. How does overhauling my profile change the relevance of having a link to a list of the newest caches in the state I live?

On my profile page, the "List Newest Caches in <State>" no longer appears. It seems to have disappeared with the 30 Sept. site update. I for one used this link frequently and would appreciate it being added back.

Perhaps not the intended impression, but it seems this would promote elitism. I don't consider that a good thing.

This past weekend it took me mountain biking in the Phoenix Sonoran Preserve. Next weekend it's taking me to the start of a 5 day backpack into the Nankoweap area of Grand Canyon where my cohorts and I will hopefully be FTF with Canyoneering-Nankoweap GC, which has been waiting close to 3.5 years without any visitors.

Two minutes? That's wishful thinking in even the best of circumstances. There's lots of things that probably need to be updated to correct that problem. Here's some possibilities: A new cache adoption email template will need to be created. The cache adoption email generator will need to be updated to use the new template. Verify cache adoption uses the new template. Verify trackable adoption uses the proper template. Trivializing changes isn't helping anyone.

I found a $10 bill once. Today I found two AA batteries and a packet of two ibuprofen pills.

You also have attended 14 event caches and it is my understanding that event caches are not used in computing the number of favorite points you have earned.

The problem is that "search for nearby geocaches" using a state doesn't necessarily return all the caches for that state. For example, when I did it for Arizona, it returned 16,175 caches. When I go to the Hide and Seek page and searched on Arizona it returned 28,949 caches. That's a big difference.

Today's reality is that software is released with minimal testing and the user's will find most of the bugs post release. This is all driven by the users desire to have it now, not later. To support that, the concept of several small frequent releases instead of large releases delivered every year or two has emerged, along with the ability to get the software without physical media. App stores for Apple, Android, and now Windows were developed to support this. That's the reality of the current environment and it's what we're stuck with for now. Actually, it's what we've demanded. Releases with a short period of bug fixes are now the norm for end user services.

I'm in Phoenix too, so I sorted your finds by terrain. I've also found all of the first 45 or so of your highest terrain caches. I have a hard time describing most of them as backcountry caches though they certainly are on desert trails where one needs to watch for venomous critters and poky things. There's nothing wrong with that. I think a cell phone is fine for the areas you have been caching. If you plan on expanding your caching to the remote areas where cell phone service is spotty, then a PLB, such as SPOT might be a good idea. I have a SPOT myself and have it with me whenever I'm off hiking/caching in remote areas. I've even had to use it once to call for help when my dirt bike broke down in BFE. The best thing to do, as others have mentioned, is to let someone know were you are going and just as importantly, when you will return. Also, let whoever that is to notify authorities when you are late and state that you are an overdue hiker, not that you are missing. Now back to those trails you've been hiking. Just because I don't consider them backcountry does not mean that one can go out and hike/cache on them without being prepared. A couple of summer's ago a cacher died from exposure trying for a FTF on a very hot afternoon on trails in the Preserve you've been hiking in. Be smart when you go out. Personally, I look for caches that are not found very often so I end up in the remote areas quite often. If you see yourself heading in that direction to, I recommend taking a look at the link in my signature. Good luck!

Yeah, it's working again. That was humorous.

Should have mentioned: Runtime Error Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.

Cool, the website stopped working.

Cycle much? Evidently not. I'll get to double digit (ooh, 10+ mph) speeds with a couple of turns of the pedals. Whatever.

It's not there because the search was made without a point of reference. What would you like the distance and bearing in relation to?