Forums Geocaching in Wisconsin General crappy logs bugging me

Viewing 15 posts - 31 through 45 (of 59 total)
  • Author
    Posts
  • #1962735

    I like your email that you cam up with Barry. If you do not mind, I may start using that when I get a 100 TFTC’s from one cacher.

    #1962736

    @Bassanio wrote:

    I don’t let crappy logs bother me too much. They do confuse me, though. There are so many great caches that get TFTC logs and I am just confused on how finders could take so little from the experience that all they want to do is type in the least amount possible to be able to log a find.

    The one thing about crappy logs that does bother me is the loss of the feeling of community that it brings with it. Without sharing your experiences, good or bad, this just becomes a numbers game. A TFTC or smiley face log tells me absolutely nothing about the cache besides that it was found. Caches are slowly being reduced to “check this box if you found this cache”. 🙁

    For many CO’s, the reward for placing a cache is the logs you receive and being able to share in the adventure with the finder. With TFTC, there is no sharing of anything and CO’s eventually won’t be overly inspired to place anything beyond a park and grab cache, since numbers mean more than adventures to too many cachers.

    Now, I’m not the most prolific cacher, so I can’t speak from the perspective of finding dozens or even hundreds of caches in a day/weekend (heck, 10 caches in a day is a lot for me). So, I get the reasoning behind some TFTC or cut-n-paste logs…I’m sure some caches are just a blur at the end of the day. I guess that’s where “play the game the way you want” comes from. Personally, I couldn’t imagine racking up cache after cache if they were so unmemorable.

    right on.

    z

    #1962737
    #1962738

    We did get a few responses back, most of them telling us where to put it (and the sun does not shine there) others I did notice when they logged one of our caches the next time the log was at least a sentence long

    #1962739

    @sweetlife wrote:

    We did get a few responses back, most of them telling us where to put it (and the sun does not shine there) others I did notice when they logged one of our caches the next time the log was at least a sentence long

    I got the same response when trying to educate a noob on the etiquette regarding puzzles caches that have an optional ALR. “Screw You. Don’t F***ing tell me how to play the game. The only requirement is to sign the log.”

    I guess if it went missing and the log sheet disappeared I could legimately delete the log though for failing to sign the log. 😉

    #1962740
    huffinpuffin2
    Participant

      @sweetlife wrote:

      We did get a few responses back, most of them telling us where to put it (and the sun does not shine there) ……..

      Seems like WisKid mentioned encountering this same sort of response/attitude, at least occasionally, in his communications as a Reviewer. Really, really hard to believe anyone responding that way. ❓

      On the positive, you did find a way to get a meaningful response! 🙂

      #1962741

      I agree, and my note to the noobs was intended to try to educate them about why writing a log is important, not chew em out for not doing it.

      Maybe if every cache owner started emailing noobs when they post lame logs, some of them would start to get the message. After all, isn’t education of new people something that the WGA and more experienced cachers should be doing?

      z[/quote]

      note to self…never post a lame log when logging zuma’s caches, to avoid being called a noob. 😀

      #1962742

      noob!

      #1962743

      @CacheNoTrace wrote:

      noob!

      😯 😛

      #1962744

      @Hitman4 wrote:

      @CacheNoTrace wrote:

      noob!

      😯 😛

      TFTP.

      z

      #1962745

      @zuma wrote:

      @Hitman4 wrote:

      @CacheNoTrace wrote:

      noob!

      😯 😛

      TFTP.

      z

      Anytime! 😆

      #1962746

      @BigJim60 wrote:

      The other day I found a cache that I had dnf’ed in the past. The cache was a camo’ed bison tube lodged in a natural crevice in the bark of a very large, very old white pine. The bison has a history of popping out of the crevice and being found on the ground. The previous finder’s log included the following: “Found on ground. Rehide better per the way this game is suposed to be played.”

      “Rehide better” in this case included carving a niche in the bark with a knife, cutting all the way through the bark to the sapwood. I can’t believe that anyone would believe that this is “the way this game is suposed to be played.”
      I was sickened by this cacher’s actions.

      That resulted in the cacche being disabled while the container was pulled and getting desapped, and allowing some time for the tree to heal. We didn’t want people thinking that it was OK to stick the cleaned container back in the gouge. We wrote a note on the cache page as to why the cache was disabled, but I doubt if the person who really needed to read it ever saw it.

      #1962747
      BigJim
      Participant

        @sandlanders wrote:

        @BigJim60 wrote:

        The other day I found a cache that I had dnf’ed in the past. The cache was a camo’ed bison tube lodged in a natural crevice in the bark of a very large, very old white pine. The bison has a history of popping out of the crevice and being found on the ground. The previous finder’s log included the following: “Found on ground. Rehide better per the way this game is suposed to be played.”

        “Rehide better” in this case included carving a niche in the bark with a knife, cutting all the way through the bark to the sapwood. I can’t believe that anyone would believe that this is “the way this game is suposed to be played.”
        I was sickened by this cacher’s actions.

        That resulted in the cacche being disabled while the container was pulled and getting desapped, and allowing some time for the tree to heal. We didn’t want people thinking that it was OK to stick the cleaned container back in the gouge. We wrote a note on the cache page as to why the cache was disabled, but I doubt if the person who really needed to read it ever saw it.

        I struggled for most of a day about whether or not I should contact that individual and express my feelings about his actions. I decided not to, but it still bothers me.

        All opinions, comments, and useless drivel I post are mine alone and do not reflect the opinions of the WGA BOD.

        #1962748

        Well, as a CO myself, TFTC logs don’t really bother me. For every one of those I get, I get several more actual logs.

        There’s a cacher near my neck of the woods who has 3 letters and 2 numbers in his name. He’s an FTF hound too. So all he writes in his logs is “FTF TFTC”.

        He did that to a few caches on the Yellow Brick Road series. The Wizard of OC tried to e-mail him about logging etiquette. But he doesn’t seem to get the message.

        Really, nothing we can do about those logs. After all, if they found the cache and physically signed the log, that’s what matters.

        My advice is this – don’t worry about the TFTC’s. For every one of those, there will be several others detailed logs. Let those TFTC cachers do their thing and we do ours.

        This topic seems to be as we have discussed this several times so I guess I should not be surprised it is still being discussed.

        I’m sure there are a hundred threads on this board alone talking about this topic.

        So time to stop with the .

        #1962749

        Honestly, I’d rather have a “TFTC” than one of my favorite logs, “Easy cache for our team to find.” Got a team in the area that puts that on EVERY cache (and never logs their DNFs) and has plazed a grand total of zero caches of their own. Doesn’t matter how hard the cache is or what went into its design or creation, it’s just “easy.” Used to really get me annoyed, now I just click the “delete” button fast.

        On the Left Side of the Road...
      Viewing 15 posts - 31 through 45 (of 59 total)
      • You must be logged in to reply to this topic.