Jump to content


+Premium Members
  • Posts

  • Joined

  • Last visited

Everything posted by stijnhommes

  1. Is it possible that they attended and simply didn't meet you? Could they have met someone else and thought that it was you? Could they have been using the word "you" more like people around here would use "Y'all"? Possible, but highly unlikely. I have accounted for every actual attendee and asked them about it. None of them seem to have met that particular cacher that day.
  2. I don't get it. Why do so many people feel entitled to log puzzle caches and multi's when they're not putting in the effort of actually going through the motions? What is next? A triple platinum membership that allows you to log caches without visiting the physical location? Either do them or don't, but don't expect cheating to be an accepted practice.
  3. I recently held my first event. Although I can account for multiple names on the list of attended people, it appears some people logged "attended" without ever coming near NYC where I held the event. Are fake event logs a thing you see often on your own events? I'm happy to allow team members of attendees to log. I'm fine with allowing logs to people who turned up later and missed us after we left the meeting spot, but I won't allow people to log when they claim to have met me when they haven't. How do you deal with this sort of thing?
  4. If you can ensure the TB ends up in the target state, it's worth asking the owner if you can hold on to it for a couple of weeks. Respect their wishes either way.
  5. If you find a travel bug in your cache, you're free to log a discovery. After all, you've seen it and the travel bug owner generally loves confirmation of where it's at. I personally refrain from taking bugs from my own cache since it adds to the experience of people visiting, but if it lies around there for long, there's no harm in taking it and dropping it elsewhere either.
  6. Thanks for giving me something to chew on. I definitely want to cram in a couple of virtuals and letterbox-hybrids since I don't often come across those. If anyone else still has suggestions, I'm open to them until August 22.
  7. On August 23, 2014, I will be visiting New York City for a week for my holiday. After checking the map, I've come to the conclusion I have nowhere near enough to see the tourist sites and find all the caches in the area (as I tried in Venice). There are simply too much caches in New York. I could go out caching for the entire week and not even clean out a single borough. So, I'm looking for recommendations. I especially enjoy caches in interesting locations or ones that have been custom built to show the hider's creativity. Which NYC cache should I not miss? "GCHTK1 - Five Star New York" looks like it's quite difficult, but everyone is raving about it, so I'll definitely give it a shot. What are your favorites?
  8. You could, but it's kind of pointless since the people who don't read cache pages are often also the kind of people who don't read instructions period. Not all of them, but...
  9. If you're not talking about QR travel bugs, then the answer is that you can't scan them...
  10. If there's no WYSIWYG editor on geocaching.com, then why not use one on your computer and copy the results to the listing page?
  11. If the owner responds to your messages (instead of the reviewer notes, you can ask them to adopt them to you. If that doesn't work, let them be archived and just submit a new page for that cache under your own name.
  12. While a GPS is not typically 100% accurate, you could try to do a so-called geo-dance when you get close. Walk in circles, walk past and see the arrow of your compass change direction as you walk past, approach from different directions and see what general area your GPS brings you to. If the same spot comes up repeatedly, chances are it's there -- with the caveat that both you and the cache owner might suffer from some coordinate errors.
  13. De officiële app heeft wel degelijk de mogelijkheid om coordinaten in te voeren. Hij is alleen verstopt. Ga even langs op het forum voor de iPhone app. Daar weten ze wel hoe het zit.
  14. If I remember correctly there are several versions of the submission form. How did you reach the one you're using? What browser are you using? Try another if it's Internet Explorer.
  15. Although finding some caches can help, I don't feel it's necessary to hiding. As long as you read and follow the rules and guidelines and are willing to put in some serious effort and creativity, you should be allowed to hide.
  16. I think that if someone logs 850 caches in a single 24 hour period, I'll have to call shenanigans. 1 day = 86400 seconds 86400 seconds/850 caches = (approximately) 101 seconds per cache. That is a full 24 hours without so much as a toilet break, food break or even a break to add gas to your car and you'd have to do the finding, opening, logging and replacing all in those 100 seconds. I've heard about multiple attacking such trails in small sections simultaneously, but I find that cheating. Everyone needs to be present at the find to claim it.
  17. If you do this, the trackable will appear in the cache you took it from until you choose to replace it somewhere. For all intents and purposes, the owner will believe it has been stolen or gone missing. Why not log the pick up and posting a detailed log to let the owner know exactly when and where you plan to move the TB? As a TB owner, I know I'd be much happier knowing someone is planning to move it, than being left in limbo over its fate...
  18. Unfortunately, there are too many people who don't ask for permission. But people on holiday is a valid reason around this time. They pass you on because a lot of people don't know who in their organization is in charge of caches. Help them along, make suggestions. If someone else near you specifically mentions their permission in the description ask for contact info to expedite your efforts to reach the right person.
  19. Your last line hits the nail on the head. If discussing it with the owner doesn't help, bring it up with the reviewer who published the cache (you can find them in the very first logbook post).
  20. You could just play Ingress... You have the inherent problem that you can't check whether people have actually visited caches. Sure you can have them leave tokens, but who says someone else won't pick those up before you come to check on them?
  21. There are just a handful of things newbies need to know about trackables: 1) How to log them. 2) Where you can and cannot place them 3) You can't hang on to them, they're someone else's property. That's all.
  22. If they might have the TB, you could try leaving a message on the TB page -- or maybe in a forum post they responded to, but as long as they don't validate their email, I don't think they'll receive note on either such message. If you have an idea where they live, you could draft local cachers to help locate them.
  23. If the CO is not doing maintenance, let the cache die out. Don't do the maintenance unless a cache is VERY special and it is better for everyone if it remains. Talk to some earlier people who found it. If it was indeed the cache, log it as found. Otherwise, not.
  24. Wow, I didn't expect it, but there are 2058 caches in a 16 km (=10 miles) radius around my house. I guess a small country gives quicker saturation...
  25. Yep, totally agree. I like to be able to search old posts. Especially if they contain unique information which isn't often repeated.
  • Create New...