Yossarian

I agree. Having the hider's name and a link to their profile in the emails would be more useful than having the reviewer's name and a link to their profile in there IMHO. (not that I have anything against reviewers)

What if (maybe a big if) scheduled PQs could be added to the queue based on each user's local time instead of all worldwide scheduled PQs being added to the queue after midnight Groundspeak time? That way they could be spaced more evenly throughout the day and there wouldn't (hopefully) be a big backlog at any one time. Of course...that wouldn't help things with the current setup if it really is taking longer than 24 hours to process them all some days.

Pocket Queries include the 5 most recent logs. I believe the GPX files on the cache pages include up to the 20 most recent logs. If there are DNFs within those 5 or 20 most recent logs, they should be included. If a DNF was say the 7th most recent log it would be included in the cache page GPX but not the PQ.

Just wondering...what does "GP" stand for?

Alternatively, on the forum main page you can click the icons to the left of the forum names to mark them as read. Those icons with then change to the IPB icon signifying that those forums have no new messages. Or if you want to mark all posts in all forums read, there's a link near the bottom of the forum main page on the right side to "Mark all posts as read".

My vote is to give Premium Members the ability to see anonymous info on how many people are viewing their caches and when but nothing more. There's no good reason to see specifically who is viewing them IMHO.

Not on geocaching.com as far as I know. You might want to check out Scaredy Cat Films' NGS Benchmark Viewer

Here's a more recent thread on the same subject: http://forums.Groundspeak.com/GC/index.php...=209292&hl= I agree that if pictures from cache/coin/TB pages are going to show up in the gallery it would be nice if they behaved the same as other pictures in the gallery when clicked on.

Not trying to stir the pot here or anything...just something that's been in the back of my mind for awhile. Let's say there's a cache hidden in some random public park somewhere. Regardless of whether the cache placer is active or not...from a legal standpoint, does that cache that's essentially abandoned in that public park actually belong to anybody? Is possession really nine tenths of the law? Any lawyers out there?

500 miles is the max.

Hmmm...works for me in Firefox 3.0.4. Have you tried clearing Firefox's cache?

If I remove the parenthesis from the end of that link it works. Where/how did you get that link?

What problem are you having exactly? Other than being slow to load when a large number of caches are in view (as usual) it's working fine for me in both IE 6.0 and Firefox.

I saved your query from above and set it to run today. I received it within a few minutes. It included 177 caches. So...it is working at least some of the time.

My understanding is that new queries go to the front of the queue, thereby delaying all the non-new ones. What I'd like to know is what exactly determines where a non-new query falls in the queue? When it was last run? How often it is scheduled to run? How old it is? Or some combination of the above?

Verify that the email address in your profile is correct and then go here to have the validation email sent to you: Link

The + and - buttons are working fine for me in both IE and FF. Try clearing your browser's cache maybe?

Welcome back to the forums, ReedKyCacheFinders!

Here's what I would do: Log out of the forums using the "Log Out" link up in the top left corner. Go to your Geocaching profile and change your password: http://www.geocaching.com/my/password.aspx Then click on the "Forums" link on the left side of the page. (*Very* important - using that specific link updates your password in the forums) Log in to the forums using the new password, making sure to use the same cAsE. I tried that on my account earlier today and it carried the new password over to the forums just fine. I changed it back and it carried the old password over just fine.

Have you tried clicking on the "Log Out" link up in the top left corner of these forums? If so, does it log you out? (It'll say "Welcome Guest" up at the top when you're logged out) If so, what happens when you then try to log in using your ReedKyCacheFinders name/password?

It does sort of exist already but it's not at all obvious. You can move the map without it refreshing by using the arrows instead of dragging the map.

There is indeed. http://www.geocaching.com/login/password.aspx

Haven't been getting what emails? You say you're getting the mailers and some PQ's so you are getting some emails... Some people have reported having success with setting up a gmail address, changing their GC account to send email to that gmail address and then having gmail forward the mail to their ISP.

I received 5 PQ's yesterday and can't remember the last time I missed the weekly mailer. Unforunately the downside of spam blocking is that legitimate email sometimes gets blocked too...more often with some ISP's than others. If you were to look at 100 different ISP's you'd likely find 100 different mixtures of spam blocking measures... Maybe GC should come up with a page to help with troubleshooting email delivery problems. One would go to the page to request that GC send a test email to their default email address and optionally have that same email Cc'd to an alternate email address. Then if the email didn't get delivered to your ISP but the Cc did get delivered to the alternate address (say a gmail address) then you would know to complain to your ISP and not Groundspeak.

I take it you and your other half have separate Geocaching accounts and email accounts? Do you both have your email spam blocking settings (if any) with your ISP set up the same? Both have geocaching.com emails whitelisted? The presence of cookies is what keeps you logged into the site. When you click the Log Out link the relevant cookies are deleted. You could try manually deleting all geocaching.com cookies and then log back in to see if that corrects the problem.