markens

Thanks, knowing this makes workaround doable. Either direct download from the page, which will come with the last 20 logs, or GSAK 'refresh data' will grab more logs. I agree, thanks for the explanation.

I ran several PQs just now and they seem to work ok. But I noticed an issue I haven't seen mentioned yet: The PQs only include logs which are newer than about five years old. Previously there was no time limit on logs included. This means I am seeing a bunch of caches in the resulting GPX file that have no logs at all. Needless to say this is a loss of useful information as there are numerous (very) lonely caches in my area. Why was the time limit implemented, and can it be removed so that the five newest logs can be included no matter the time interval (as before)? Thanks much.

This is a very good change, thanks.

Interesting. I have rarely seen a noticeable delay in loading the current "my" page, sometimes with as many as 150 log entries. It seems that you saying that the new layout will perform worse than the existing one. I look at this list quite often, almost daily. The list is especially useful after a trip out of town with many finds. The main usefulness for me is being able to see at a glance a representation of my recent caching activity. And I find that 30 day's worth is a perfect-sized chunk to accomplish this. The past "n" logs does not give this to me, because it is missing the time element in an obvious fashion. Similarly, the graphs on the statistics page (while useful in their own right), also do not present information in the same way. I find it very useful to see the types of caches, etc, in this representation, and be able to easily click on specific cache listings or logs. I also find it very useful after a trip out of town (or a particularly active local cache outing) to be able to quickly access recent logs. Not just finds, but other logs as well (including TBs). I do this for a number of purposes, including setting watches on caches for various reasons, awarding favorite points, or simply going back to ensure that my logs make sense. Limiting to 20 logs negates much of this usefulness. I prefer the data to be in one list, on one page. Dynamically loading the logs on individual cache pages seems to work well in that context -- keep scrolling to keep getting data. But this is not what I want for the past 30 days logs, since it requires specific action on my part to receive the data and I lose the "snapshot" characteristic of the data. Similarly, splitting into pages negates the benefits of seeing everything on one page as a snapshot. The page where performance is definitely an issue is when all logs are requested. This seems to load all logs on one page at one time, and indeed takes long enough to complete (for my 9000 records) that it totally freezes my browser for an unreasonable amount of time. Please address this performance issue! Thanks for listening.

Missing from this statement is how many of our own recent logs will be viewable. As a bunch of people have stated, we would like to be able to see the most recent 30 days worth of logs, as it is a very useful snapshot of our own recent activity. There is way too much information in the all logs menu selection (almost 9000 records for me), and way too little information if just the most recent 5 days or so is displayed. So please give us the option to see 30 days worth of our own recent logs!

Echoing comments which have mostly already been made: 1) I don't want to see friend's logs on this page. Give me a way to turn it off. 2) I don't want to see recently viewed caches on this page. Give me a way to turn it off. 3) I DO want to see MY logs for the past 30 days. This is what I use most on this page. Please let me do it. 4) There is way too much white space on the page, requiring much scrolling to see what I want. The compact listing on the old page was good.

I also use iGeocacher on my iTouch, as a replacement for cachemate on my palm. It gives me a quick way to download and access large PQ collections on my iTouch very easily. In addition, I use the Groundspeak Geocaching app for quick local updates with its Saved Caches feature. It's still a bit rough, but has useful features. These two apps total about 90% of what I've paid for apps (!), but they each provide useful functionality.

FYI if you haven't seen it -- There is an article about geocaching on the front page of today's Palo Alto Daily News. The headline is "GPS games cause headaches" and is mostly about a number of caches found by rangers in Edgewood Nature Preserve that are in sensitive-habitat areas. There's even a color picture of a ranger with an "area closed" sign in the background. Definitely an interesting read.

Thanks, Jeremy -- I thought it might be doing something like that but just wanted to check. This was the first time I clicked "yesterday" for a PQ; now that I know that it might cause the PQ to run "today," I won't do it until "tomorrow!" --markens

A slightly different PQ problem, in that I received data that I didn't ask for: I have two queries which were inactive (no days checked), and I wanted to enable them for Tuesdays. So (today, Weds, around noon PDT) I checked the Tues box for each of them. Lo and behold, within an hour and a half I received PQ results mailed to me. The Tuesday queries ran Weds at 12:03 and 1:17pm. I would not have expected this. And this would obviously be a problem if I was close to my daily limit and actually wanted to run others today. Thanks! --markens

Looks like Marky and I are seeing effects of the same (mis)behavior. Patterns in my logs are very similar to his. The mail problem cleared up for me very soon after my last post, and mail has been received okay since. --markens

I've also started seeing email problems from signal.Groundspeak.com over the past week, although my log entries are different. I have many entries like this in my log: Jun 3 13:10:34 NOQUEUE: Null connection from signal.Groundspeak.com [63.251.163.165] Jun 3 13:10:37 NOQUEUE: Null connection from signal.Groundspeak.com [63.251.163.165] Jun 3 14:00:34 NOQUEUE: Null connection from signal.Groundspeak.com [63.251.163.165] Jun 3 14:17:11 NOQUEUE: Null connection from signal.Groundspeak.com [63.251.163.165] Looking at the sendmail source code indicates that this condition is only logged in one of two situations: a QUIT comand is sent prior to MAIL (or EXPN, VRFY, or ETRN) too many unrecognized commands are received The occasional watchlist email arrives okay. But several pocket queries are MIA. I'll also contact Elias directly. Thanks...