Jump to content

PatrickD

Members
  • Posts

    35
  • Joined

  • Last visited

Everything posted by PatrickD

  1. I usually do and make the instructions clear that "this is not a prize to keep". I think I did with these too, but my memory is hazy.
  2. There's two different people in two different states with two of my trackables that have had them for quite a while and they keep putting them in a cache and then immediately taking them out. Most of these caches they're doing it with are just a few miles apart...but hundreds (or thousands) of miles from where they both started and hundreds of miles away from their intended destination. I really want to message these people to tell them, "Just leave it. STOP TAKING IT WITH YOU! Let someone else move it along!" ...but I don't. The last time I did that (in a very polite manner, not like I just typed), the trackable mysteriously disappeared. Come on people...these trackables each have goals. You're not helping. Stop hoarding trackables!
  3. I agree that it would make sense to start at the home coordinates...or else dropping it off 2000 miles away from home makes that travel meaningless. What I've done with mine to get around this inaccuracy is log them in and out of the cache nearest to my home (or just drop them there to start).
  4. I'm amused that their hosts file has the ad servers at the dotcom company I work for listed. However, it also has our cookie server. Anyone who uses this file and looks for a new job on our rather popular job web site is going to have a tough time.
  5. Exactly. It might be hard for someone to get a TB out of a 5/5 cache, but the possibility exists. There's hope! If the TB is at your house, there's no hope until you get it back out in the wild.
  6. Mmmm... You can't go wrong with free pizza. ...especially after a long day of caching.
  7. Don't give out the tag number, but the TB number found on the bug's page (like TBHG4D) is okay. As for searching, were you looking for this page? http://www.geocaching.com/track/search.aspx
  8. You probably shouldn't have written it in the paper log inside the cache, but I don't think that's too big of a deal. If it was online, it would be available to troublemakers who hadn't even found that cache (or any cache).
  9. Perhaps it's time to close down the graveyards and give those TBs a "proper burial"...so to speak.
  10. Pick a few other caches to do near that 1/1 cache so that if you don't find the 1/1, you can try another one. ...or so if you have as much fun as most of us do, you can go find another one without having to go home first.
  11. I'm suddenly getting all these evil ideas for encasing a cache in a thick block of ice.
  12. Arrgh! I searched for a thread like that. I guess I didn't search back far enough. Oops. Sorry...
  13. I'm curious what kind of vehicles people drive while geocaching. I think my curiosity comes from the fact that I probably drive one of the least likely vehicles...one that can barely handle icy roads. Off road? Mud? Don't even think about it. My car can be seen in photos with this travel bug. In the Massachusetts winter, I refer to my Nissan 350Z as "my three thousand pound, 287 horsepower death machine." So when everyone else heads out to find a cache, what pulls out of your garage?
  14. PatrickD

    Small Caches

    I have just one cache (so far). It's not micro and not "regular" (more like the size of a kid's shoebox) and I was wishing the small size was available when I placed it. I changed it to "small" a couple hours ago and it was just approved about an hour ago. Good timing!
  15. Speaking as a web developer... I don't think cookies would have anything to do with it. When someone goes to log a find, check to see if they've already got one. If so, don't allow another find to be logged. Database lookups, not cookies. Of course, for those caches that allow multiple finds (for whatever reason) there would need to be some sort of flag set by the cache owner that either allows it or bans it.
  16. Restarting a half dozen old ones all about the same topic? That's excessive.
  17. PatrickD

    New Feature

    It's there now, isn't it? It wasn't when I posted...but it is now.
  18. That doesn't show up if you edit right away.
  19. My feeling is that because a Travel Bug is "a trackable item that moves from place to place" that you shouldn't log it unless you actually DO help it move. Otherwise you're taking credit for doing absolutely nothing. It's kind of like showing up at a blood drive, taking an "I gave blood" sticker, and walking out. If there are two YJ TBs and you want credit for both, why not move them both...perhaps to two different caches? Keep the travel bugs moving.
  20. If you've worked for weeks/months/years to plan your cache, waiting a day longer to have it approved is just a drop in the bucket. The turnaround time is still relatively short.
  21. PatrickD

    New Feature

    Any ETA on when the "Small" size cache (between "micro' and "regular") will be added?
  22. Good point, but less words is better. "Visit www.Groundspeak.com to learn about me and how you can help me on my adventure" Also, I think there should be just a TOUCH more space between the Geocaching logo, the center text, and the bottom text so that it doesn't all blend together quite so much. ...but I'm just a nitpicky creative designer.
  23. I must admit that it annoyed me when I recently attempted what should have been an "easy" cache, bushwacked through the forest for a good 20 minutes, and realized I was on the wrong side of a river with no bridge in sight. ...and the cache was right on the other side. By the time I made my way out of the woods, it was getting dark. Had there been a parking suggestion, it would have saved me some time and a long drive out there for nothing. Of course, I could have checked MapQuest and zoomed in to find out exactly what side of the river it was on, but that's kind of like cheating and something I've tried to avoid doing.
  24. I love the new wording! Thank you VERY much!
×
×
  • Create New...