Jump to content

rosebud55112

+Premium Members
  • Posts

    253
  • Joined

  • Last visited

Everything posted by rosebud55112

  1. I’ve got a couple of examples of Challenge caches that I discussed with my reviewers and had declined. Although I was a little upset at the times, I’m now thankful that the reviewers spared me from the record-keeping that would have been required on my part. The New Year’s Resolution Challenge-Find this cache and log it (make the resolution), then find and log a cache for each of the following 31 days (complete the resolution). My original idea required the finder to actually log finds on each of the following 31 days- and I thought I’d follow along and make sure that the actual posting dates matched the find dates and extended for the 31 consecutive days afterward. Now I look back and imagine what a nightmare that would be to have to follow up on that, and remove finds if someone missed a day. The Lottery Challenge- Find a cache with posted coordinates after the decimal point matched the daily Lottery numbers. Minnesota (and a lot of other states) had (has?) a daily lottery where three numbers, each in the range of 0-9, were picked. So if the 2/26/18 winning numbers were 4-5-4, then if you found a cache at N XX XX.XXX W XX XX.454 today, you would qualify. Another one that would be a pain for me to verify, as well as some logistics issues for cachers. Both of these were proposed many years ago, I think even before the changes that took place in early 2013. I’m very glad that my local reviewers convinced me I didn’t really want to do these.
  2. Not a DNF, but had we shown up a couple hours earlier it probably would have been. About a year ago, my son and I were visiting Salt Lake City for a competition he was in. After practice on Friday morning, we grabbed some lunch, and since we both like touring State Capitol buildings, we headed up to it. Found some nearby parking, and were walking up to the Virtual in front of it when he pointed out how unusual it was that there was nobody around. Usually, something is occurring at a capitol building—school field trips, protests, government workers on their way somewhere—but it was pretty quiet. We gathered our info/picture for the virtual, and went in the building. There was no one around telling us we couldn’t --it was practically deserted in there, too. We gave ourselves a self-guided tour of the building and then headed back to our car. That evening, we learned that there had been a bomb scare at the capitol building earlier in the day. By the time we got there, the State Police had determined that what was thought to be a bomb was not, in fact, a bomb, and they and all the media had left. Of course, most of the workers had been evacuated earlier, and, since it was such a beautiful Spring day, very few had come back.
  3. Did you receive an email about it first? Can I still hope my physical mailbox has a surprise for me even though my electronic one didn't?
  4. I'm more interested in why they want to discuss sorry caches. Discussing great caches is much more interesting.
  5. I don't trust the elevations that Project GC is pulling in necessarily anyway. According to them, my lowest elevation is GC2BG62, at -10 feet. This is near a river in Rhode Island. Since the river is flowing into the ocean (about 1 mile away), rather than the ocean flowing into the river valley, I'm not sure how it could even pick up anything at a below-sea-level altitude there. A couple other finds of mine further upstream are also listed as being below sea level.
  6. I got a souvenir for the day of the eclipse while on my way to our viewing site. Groundspeak just happens to call it the Nebraska souvenir.
  7. After all the complaining and whining about who got the rewards this time, I wouldn't be surprised if they decide to never do any project like this again.
  8. Yes that could be it. I have one locationless/moving cache, so that plus my duplicate find would explain the difference of two. Thanks for clearing that up for me.
  9. Currently, I have 4304 finds on 4303 unique caches, plus 7 Lab cache finds totaling 4311 finds. On my Statistics page, if I sum up all of the numbers in each category shown, I get 4311, or 4304 for those where Lab caches are specifically excluded, except for the "Distance to Finds" chart. On that chart, the sum of the amounts shown in the various categories is 4302. Since the chart states that Lab caches are not counted, I would expect a total of 4304. I could even understand 4303 if the “double find” cache is excluded for the second find. The only plausible explanation I can think of is that the mileage chart isn’t counting the “double find” cache at all. Not a big deal if this is the case, but odd. Or maybe two caches are for example, exactly 10 miles away, and not being picked up by the <10 or >10 categories? Is anybody else noticing this situation? If so, do you have any caches where you have logged multiple finds? FTR, my double find cache is GC1H5VH, which was a challenge cache which invited you to make multiple finds if you complete the challenge multiple times. I logged this twice in my first year of caching, before realizing that this is generally looked down upon. Still, as it’s part of my history, I’m keeping it this way.
  10. I saw this this morning (as a M:tG player as well) and my heart just sank. This will not work out well for geocaching. Trackable loss, and cache losses to occur. This seems to be an idea that someone at WotC had, but didn't discuss with Groundspeak.
  11. It looks like Accounts Payable at Groundspeak forgot to send out the CO checks for New York this pay period. I get mine direct deposit; I'll have to see if the Minnesota checks were sent. Yep, mine went through. Looks like a localized incident.
  12. Nutlady, as a cacher who on occasion will rush out to try to grab an FTF, and who has occasionally gotten to a cache with no find logs online only to find a name or two on the logbook, I will tell you that you are doing absolutely nothing wrong, and should not feel like crud. If other cachers are trying to make you feel like crud, then they are in the wrong. Others have mentioned a "FTF- more later" approach, which is what I will do if I do get lucky, but even that is not necessary. If you wait until it is convenient to you to log your finds, as described in your original post "wait until I get home" and "with a few hours between me finding the caches and logging the find" you are notbeing rude, disrepectful, or a bad cacher in any way. If you were intentionally waiting beyond the time when you would/could log, rubbing your hands together and cackling about all the other disappointed FTF hunters out there, well that would be a different story. But rest assured, your actions are perfectly fine. Also note that the 2TF may not be trying to make you feel bad, but just stating a fact. If I'm 2TF but the FTF hasn't logged their find yet, I will still log mine stating something like "2TF-more later". That's not meant as an indictment on the non-logged FTFer, but again is just a courtesy to others who might be on the hunt. In other words, play the game as you have been playing, don't worry about disappointing others, and don't let them make you feel bad. It's a game. It should be fun. Have fun.
  13. That's because GOD works in mysterious ways.
  14. Is the other person local? When I'm in the period before I go travelling, I will often find a cache near where I will be staying, and then sort of use that as an anchor to look at other caches in the area. For example, one day I will open that cache up and then go to the large map and check out the area to the south of it. The next day, I may pull up that same cache and then look at caches to the east. The next day to the north. Or if I'm building a booklist of the caches in the area, I may open it to the first cache on that list and do the same. Not that I plan to do it each day, but check things out in my spare time.
  15. Events certainly grab your attention this way.
  16. At the time of my post, before the post ahead of mine was edited, it mentioned the specific cache. Thankfully, that has been fixed.
  17. Thanks, guys, but I don't think you're supposed to be discussing specific cache solutions here.
  18. And that is greatly appreciated by (at least some of)us in the area. Although lately my phone and WhereYouGo don't want to cooperate, so I haven't picked up any of yours for a while. Oh my goodness, I see it's been a year since the HHXI one. I gotta get this figured out.
  19. And don't feel bad about this at all--you helped a traveler travel. that's what you're supposed to do. There is always a risk when you drop a traveler that unless you immediately log the find and drop, someone else may find that cache and pick up the traveler before you can make your log. Even if you drop in the morning, and that evening at home log everything, the traveler may have been picked up. If the other person didn't realize it was a fresh drop, or is impatient, they may have grabbed it from you before you could log it into the cache. No problem.
  20. While that is certainly true, by simply stating that the smaller region must be >10%, the spirit of the challenge is maintained. Although is someone legitimately could cover over 50% of the globe, their "qualifying" area would start to shrink, rather than grow, but I don't think that that's going to be an issue in reality.
  21. If you choose to set up a new account for mom, and want to give her credit for any of the finds under your current account that she was with you at, you can do that. Your account will show you which days the two of you found the cache, and you can add those finds to her accounts on those same days. If you do that, and are going back very far in time, you may want to include a statement like "Originally found with my son Justin, now adding under my own account" or similar to explain what is going on. Sometimes COs get a little suspicious about delayed logs, and this will help show that there's nothing hinky going on. That's especially true if the cache has been archived since the time the two of you originally found it.
  22. If you mark these as found after you adopt them, here's what the situation will be: 98% of the people in your area won't even notice that you are both the new owner and have a find on the cache, especially once your find log moves down the cache page a ways. of the remaining 2% who do notice, some will assume that you made the find before adopting the caches, particularly if you keep the original CO's credit on the cache page-something like "Cache Owner: Original Guy (adopted by gasbottle)" Of the portion who do notice the order of adoption/find, some won't care or think any less of you for finding after adoption. Of the remaining few cachers who do notice, and do care about it, they may think of you as being anywhere along the spectrum of being a little needy to being the second coming of Hitler. So the questions to ask are: "Do I personally want these as finds, versus owned caches?" and "Do I care that some minuscule number of cachers think I am a demon from Hell for finding my adopted cache?" Your own answers to those questions will tell you whether to find these.
×
×
  • Create New...