Someone asked me why I was doing a push for maintenance right now. It is pretty simple really. We have Geocoinfest coming up, we don't want to have a ton of empty/lost caches around for them to deal with, and second there is winter coming on. Once October/November hits, there will be no ability to reach some of the caches, and the desire to go out in the cold keeps others from being checked.
The result is bombing you now, rather then in the middle of winter when we can do nothing about them. So expect to be hit with a quick note if you have a cache that is under the weather, or missing for some time. I am trying to sort out the Difficulty 5 caches, so that they don't get flagged. Many times people look for a few minutes and leave and say they looked. That is the purpose of those caches. You may get a note, please respond, or just to a quick check to see if it is still there. People like to know they are looking for something, and that it has not fallen out of the tree and rolled into the storm drain.
Well I am trying to skim through 14000 caches as fast as I can. I had set a goal to get it done by mid month. I am doing a quick look for problem caches. Caches that appear to be missing. I don't look to hard or evaluate 10+ DNF if the difficulty is high. But most the others just get ignored and I wanted to flag them so people can go and check on them before the snow flies.
If you get the message, don't panic. You can post a note saying that you are going to get to it in 3-4 weeks. I would like some info that you are checking on it. If someone has flagged your cache as "Needs archived" that is almost like me letting you know. If you have not logged on in 6+ months and I see a Needs Archived I may let it go away. I always give you time. Time to get home from your vacation and let me know that you are going to go out. Just throw a note up.
On the outside chance that it gets archived. Let me know soon. As soon as it is up and running and as long as it meets current listing requirements I will unarchive it. Some people swoop on the sites, so let me know what you are doing so I do not publish a new cache there. As allways let me know the GC code for the cache you are communicating to me.
A few of you have asked about how I review and how you can speed up your personal review. I thought I would take a moment and see if I can throw some light. I sit down at my computer and look at the list of caches to be reviewed. I started with the oldest GC code. That cache (in theory) has been floating around for a week or more and is waiting to be reviewed. So I start there. It does not do any good if you change your placement date back a week or two or three. That is the order I go in. (remember this is just me not other reviewers). Some cachers dump a bunch of caches at one time. I put those aside until I am done. Why? If a cacher places a large number why should I make others wait until I am done with his ten caches. (thats my opinion).
Also, some are slow learners (like myelf) I have learned that there are certain people that I know may have a few problems with their caches. I may set their aside until I clear the others as well. Again, why should I spend 20 minutes looking at one, and punishing other cachers for the foolishness of the problem cacher.
I want to get them published asap. Nothing annoyed me more then waiting for 3 days to get my cache published. I understood the reviewer had a life, but I wanted to see my stuff published.
How can you avoid having your caches held onto for a little bit?
- Read the guidelines - I am surprised by the little mistakes.
- Check proximity - look at the map. If there is another cache nearby know if it is far enough away. Please dont ask me to place a cache 500' away just because you didn't look. I have some leeway, but wadable rivers, buildings, parking lots, freeways with a nearby crossing, are not reasons to place a cache nearby. Those will be looked at on a case by case basis. If your cache is clever, time was spent putting it together, and needs to be location specific, email me and we can talk. Ultimatly a micro 500' from a micro will not get much of a second look. Something fun and clever might be. (note the word - might). (i may do an entire discussion on this at some point)
- Think about your placement, and read it through. Have your boyfriend, girlfriend, husband, wife, or kid look to see if something is right/wrong.
Try and keep all the notes on your cache page. I usually post emails I get on there as well that I feel is relavant. Even after the cache is gone, I can look at the long gone notes to see problems and instructions I (or another reviewer) may have given you. If we say no to proximity, then you move it and get it approved, then move your cache to where we said no, or something similar, then your cache may be archived, with no warning. If I get swine flue, and I am sitting in the hospital for weeks in a coma, then another reviewer will step in, they will want to see my concerns and your responses and how we were working on them.
Think. Some things are legal, but think if its smart. Can I put a cache on my back porch, most assuridly. Do you want people wandering around on your back porch at 3am looking for that micro stuck to your back door? We try and point out unwise caches.
Well, back the the reviewing. I wish this site allowed for people to comment. Then I would know if someone actually cared or visited.
-may the forks be with you-