Jump to content

mtn-man

+Charter Members
  • Posts

    7212
  • Joined

  • Last visited

Everything posted by mtn-man

  1. Ouch. Yeah, that kind of bothered me. I know Erik well and there is a good reason why he reviews much of the world. Since you don't know his background, you should probably not insult him. As a good friend of his, I know he is more than qualified to handle the situation. In this case with his warning, he is simply doing his job. If he had not posted that note, the people would be on him for not doing his job. He has not archived the cache yet, and I am sure he will be working with Groundspeak directly on this one due to the nature of the chain of events set in place with all of this. And moose61, thank you.
  2. Thanks, done. Moving to the GPS and Technology forum area. You will get better answers there I think.
  3. In your case, it was one of the fake accounts logging simply to disrupt the system. If you notice, the log is gone from your cache page. That is because I deleted it since it was spamming and unwarranted. I got your back on that one Chief301.
  4. I'm voting with my keyboard. I've sent a complaint regarding the fact that the OP has admitted to trolling to Groundspeak. Just as he can complain about a cache by posting a Needs Archived note on a cache, the community can also complain about users via email to Groundspeak. This is suppose to be a game. In my opinion, disruptive participants should be thrown out of the game just like in any other game so the rest can enjoy the activity and have fun. Would the contact[at]roundspeak[dot]com address be the most appropriate one to send a complaint to? No, it would be at geocaching, not at Groundspeak. I don't think he deserves a total ban. I think some time off to think about the cause and effect on the community is warranted. That just my opinion though. It is up to the folks in Seattle to decide.
  5. I'm voting with my keyboard. I've sent a complaint regarding the fact that the OP has admitted to trolling to Groundspeak. Just as he can complain about a cache by posting a Needs Archived note on a cache, the community can also complain about users via email to Groundspeak. This is suppose to be a game. In my opinion, disruptive participants should be thrown out of the game just like in any other game so the rest can enjoy the activity and have fun.
  6. Disclaimer: At no point was I advocating that anyone should run over any dog, especially ones wearing glasses. We both thank you.
  7. So... you are admitting that this whole thing was a troll. Nice. Thanks for the experiment. This is their site, their guidelines, and their company for which to make a profit. Yes... there is no secret that they keep some special caches alive for the sake of publicity. The space shuttle and deep sea vents are two examples. I wish that you had just asked. We would gladly have told you and you could have avoided all this angst. Oh great, thanks SwineFlew. I don't really need a life. I love having to spend all day in the forums and tending to the hornets you kicked. It is really tough for me at work right now since we have a lot going, but who cares. It is all about you and your little experiment, eh? Right. Now you admit that you are testing Groundspeak to boot? Oh yeah, nice. Dadgummed if they don't archive it, dadgummed if they do archive it. Epic fail.
  8. Sorry Ringbone. You have no hides or finds. Please stick to posting with your player account, eh?
  9. That's not an app problem, that's a Cache Owner problem. If they are not using the "Update Co-ordinates" log type, then they are doing it wrong. Send the CO a polite email and ask them to use that method. If you are ignored, email the reviewer who published the cache and ask them to get involved. But yes 11 feet, that's pretty miniscule as the others have said. My best GPS can only get down to 3 metres under ideal circumstances (3M =~ 9 feet). The co-ordinates in logs issue affects everyone with Pocket Queries too, as we only get the last 5 log entries in a GPX file. Exactly, with regard to what I made bold above. Unless you *and* the cache owner *both* use one of these below, you should always expect that you will need to expand your search unless you are just lucky and the satellites align just right for you.
  10. If it was moved only 11 feet, then you should have still been able to find it due to estimated position error (EPE). Did you even notice your EPE when you were looking? Your typical EPE with a phone is much higher than that unless you are in a field with no trees or in the middle of a parking lot. I rarely see less than 10 feet EPE, and anything less than that is probably outside of your phone's actual ability to resolve the location down further. Yesterday I was as low as 10 foot EPE and as high as 125 foot EPE and kept having to go in and out of the trees to get some sort of acceptable updating. I found the cache, a micro in pine trees. Using your phone (or a GPSr), if you think you can go to the 0 foot mark, look down and the cache will be at your feet, you will be unsuccessful and disappointed most of the time. You need to understand that the person that placed the cache might be off a bit when they hid it, and you might be off a bit as you look for it. Combine their EPE and your EPE, and you will soon learn that you must expand your search beyond 10, 25 or even 50 feet sometimes. (When the phone settled down, it varied I was from about 15 to 20 feet away as I signed the logbook. The cache owner can update small moves of under a few hundred feet without involving the reviewer. They have to post an "Update Coordinates" log to do this. The cache owner may not be aware of the proper way to do this. You can write to them and ask them to update it, or you can write the reviewer that published the cache and ask them to update it.
  11. So I guess you thought that the guy who logged it as "My son and I swung by here aver leaving mt. Everest" wasn't suspicious (and I repeat that a log for another is 4 days after he attended and event here). What he said was "rash". You found one. As has been mentioned, considering the "Greetings from Germany" crowd, I tend to agree with knowschad. This isn't a typical virtual. I also cannot find the person that logged the find on this cache in question and had logged an event in CA four days before. It is possible though. I left Atlanta on Friday morning last week and found a few caches in Dallas, TX while waiting to get to work. The next day I logged a cache in Hartford, CT after finishing work for the day (in the dark and buried in snow). The next morning I was back in Atlanta for a 5:00 PM hockey game, and we usually get there just over an hour before the games so we can enter as the gates open and watch warm-ups and chat with our pals. If you want to doubt the validity of my finds, I will be happy to show you my AirTran Visa card bill.
  12. Well, to be honest, that virtual was probably partly archived because folks could easily log that one without even being there. I live like 10 miles from it and realized there was nothing I had to do to even log it. The South Pole one at least requires a picture. No, that cache was archived by the owner. It was their choice. There was no "Need Archived" note by anyone, no reviewer or Groundspeak involvement. A cache owner can archive their cache at any time if they want, and they did. It is completely different to the very sad chain of events set in motion by this person's actions with the armchair "Needs Archived" log they have posted.
  13. The admin explains on the cache page why a traditional would not be feasible. They must not have even clicked through to the actual cache. Probably would have been a good idea before posting that it would be an awesome spot for a real cache. I would love to see someone open that container with their "please don't let my fingers get frostbite in seconds" gloves on.
  14. You will get better answers in the proper forum. I am going to move your topic to the United Kingdom and Ireland forum.
  15. I would rather keep the topic open honestly. A better tact here would be to tell people to get on topic or get out of the topic. Drop the side topic please or we will ask you to post no further in this topic, on topic or not. Perhaps I will go back this evening and remove some of the side discussions to get the topic back to the main discussion.
  16. Just so you know, without a logbook, the geocache cannot be published. That is the one of the main requirements. It is good to keep caches close to you so that in case you make a mistake, it is easy for you to correct. Hopefully you can get a cache placed near you in the future!
  17. You've been alive since Shakespeare's Chaucer's time, I take it? This golden era where nobody talked about sex had to be before that. Your comments are irrelevant to the grand scheme of the topic. He never defined the time frame, and frankly who cares about the exact point in time when his referenced societal change took place. The change is indeed a fact and when it happened doesn't matter. His point remains, and is on topic.
  18. Go here and post the problem. Developers rarely read the forums and concentrate on the Feedback Site. Post there and vote for the problem so they notice it. http://feedback.geocaching.com/forums/75279-geocaching-for-android/suggestions/1408321-hi-version-1-1-3-downloaded-and-it-is-failing-to-?ref=title You login info is the same.
  19. I have quite a different type of milestone coming up. I am approaching my tenth year anniversary. It has been a fun thing to watch grow.
×
×
  • Create New...