Chwiliwr

To answer the OP. There is nothing to stop a reviewer going to find a traditional cache immediately after it gets published. What was said was that I would generally wait 24 hours to do so not that I WILL do so in EVERY case. Of the 650+ caches published since I became a reviewer I have found 27 of them before any other cacher. 5 the same day with the rest ranging from overnight to 9 days with more than half already looked for by other cachers who didn't find them. Only one was under an hour and there were at least 5 other cachers that could have got to the cache before me considering the distance involved. I think that I have genrally kept to what I said that I would do. The puzzle and the multi that I was first on in this period were specifically created to allow me to try for first and had no information on the listing that could help me with them. (Thanks to the CO's that thought of this for me.) I am not directing this to the OP personally but to the faceless private FB posters that caused this question of my integrity to be raised. Saying one thing to my face and then making inuendoes and accusations about my integrity in a private forum should not happen. If you have a problem with my caching the way I do then talk to me about it and stop hiding behind private FB posts. I thought that the caching community in this state were a wonderful group. Now I start to wonder if I was wrong. Corrected some spelling

Whilst the oldest cache was physically placed is May 2000 some owners have put a placed date before that. I have always assumed the earlier years in the 'placed date' part of the query system are to catch these caches.

I had to change a number of queries as a result of the change to add in 2014 to the system. I did notice that the earliest date now seems to be January 1, 1998 instead of 1997.

As already identified the size of the list is the problem. Up to about 3000 in the watchlist the problem occurs occasionaly after that the bigger the list the more the problem occurs. If you get close to the 5000 limit for the watchlist it occurs all the time unless you jag a quite time on the servers. This happened to me a little while ago when I just kept adding more than I deleted. A workaround is to create some bookmarks and transfer what you want to them (I did that through the GSAK API) then set the notify option on the bookmarks so you keep getting the emails. Once you are sure you got all the ones you want to keep via the bookmarks delete the whole watchlist in one go via that option and then build it up again or just keep the booklists.

As your a premium member another way is to examine the 'All Finds' GPX file in a word processor and look for entries that have two found logs for the one cache. As long as you haven't made too many 'note' logs you should be able to pick up the multiple logs per cache entries. A quick way of finding the logs in the GPX file is to search for characters 'Groundspeak:log id' .

I would suggest that you swap the green and gold colours around or perhaps consider having the writing on that side in black or green as the writing blends in too much into the gold background.

I don't think that they were related to your problem as I get them in the previous version of Firefox as well. Edit to clean up some mistakes

A couple of days ago I noticed a 'published' mail and printed out the listing for the cache and subsequently found it but by the time I returned home the cache had been 'retracted'. Only the fact that I had put a watch on the cache before leaving home advised me of this as there was no 'retract' notification even though it was set up in the notification area. As this is the first time I have actually seen a 'retract' it is hard to tell if this is a fault of the notify service not working at that time or that there could be a fault in the code relating to the retract notification only. Have others got retract notifications. The cache is still not published so only TPTB can see the listing. (GCV0JT)

Most computers and programs do not store the date in any way that is readily readable by humans and it a conversion of some sort by the system that displays it into a month/day/year, .. etc on the displays. That is why I would prefer to have it as user preference as suggested by Jeremy but the effort involved may not be worth it. The 'Hidden' date on the main cache page and on the 'My Account' page are the most confusing date for those not used to the M/D/YYYY format. On the 'My Account' page it isn't quite as confusing due to the dates being in a list but on the main cache page it is seen in isolation so can be frustrating at times for those not used to this format. (Or do not know that it COULD be in that format) Of all the main pages I go to it is these two dates and the timestamps on various pages that the month is not spelt out in words, either fully like 'January' or part like 'Jan'. I would therefore suggest that Jeremy consider changing these two displays of date to use the full or part spellings of the month. They would then be consistent with the displays of dates on the rest of the system, apart from the timestamps but they could be changed also to be consistent. It does nothing for those that use different spellings of the months but they already have this problem with all the other dates displayed on the site. I feel that this would immediately solve most of the ‘confusion’ factor that started this discussion in the first place and makes the personal preference option for dates less of a priority. On a slightly different tangent all the dates I see from the site are in the format m/d/y except for one page that shows dates as dd mmm yy. Is this page coded differently to pick up my PC options for dates. I couldn't tell from the source code with my limited html knowledge. The page concerned is the one that gets displayed as the result of the list newest in Western Australia search link from the 'My account' page (http://www.geocaching.com/seek/nearest.aspx?state_id=56) search.

If you read the timestamps at the bottom of the cache page they will generally give you an indication of the time if there has been no logs to the cache. Last update will generally mean the published time. Compare that to the current time (On the cache listing) to see how much elapsed time there has been.

Jeremy I can see that you may have already decided to have an 'alpha' + 'numeric' with the 'alpha' meaning something like 'p = parking' but from experience in designing and updating a code set for a large law enforcement database you will come to a point where you get to a code that will not actually mean what you originally meant it to. You are far better off not having the first two characters mean anything other than the sequence they should be in for the cache they are being associated with. The benefits of this approach is firstly you can also get rid of a significant amount of code to do with checking as the entry page can sequence them for you (ie number them) Secondly, if they have no meaning apart from the sequencing, then there will never be any questioning or arguments over what letter should be for what. Thirdly you open it up to have as many types of waypoints that you need by using only the description to describe them. Finally a sequence approach allows an owner to order mutlple types of waypoints in a logical order that he wants and not having them ordered by type, which may not be appropriate for him. (This may have been covered somewhere but both topics have a lot of replies and I didn't see if it was)

There was definately something wrong with mine yesterday as I was with a cache owner who had 3 published whilst I was there but I never got any notifications. Talking with another cacher at one of the caches he didn't receive any either and only found out by a lucky refresh. This was in Western Australia

The only way to check if it is GSAK or the operating system is to minimise all the windows shown on the task bar one at a time until you have only the rogue one left. If you can see a window still there then it is GSAK opening it but if you can't it is more likely to be the operating system but not always as it can still be GSAK but more difficult to prove one way or the other. If you click on the rogue one when all other windows are minimised and the main GSAK windows pops up then it is child window of GSAK in some way and would need to be tracked down by Clyde. By the way it isn't something new to the beta as it has happened to me once out of about 25 starts when I trialled GSAK about 3 months ago. Stopping the main window and restarting fixed whatever it was. (Via the task bar)

The message at the top of the map starts 'This is a red herring......' . If you cannot see it then you are not looking hard enough at those dots and dashes.