Logging etiqutte - long logs

[+BaSHful]

In recent weeks I have changed the nature of the logs I write which has prompted one cache owner to take me to task and ask me to change (shorten) the log I wrote. I have also had feedback from another cache owner who enjoyed reading about my experiences.

 

I tend (mostly) to cache one day a week and typically find 30 to 50 caches in that day. The practice I have recently adopted is to write a comprehensive account for the whole day (400 to 600 words) and then copy and paste it into every log. If there is a major issue with any particular cache I will raise a separate "Needs Maintenance" log for it. I see this as a compromise between having something (hopefully) interesting to say and actually getting the logging completed. And, yes, it might eventually improve my GSAK badge for average length of log.

 

I welcome some honest feedback on this subject. I suspect there might be a range of views.....

 

If it helps, these are some of my recent logs:-

http://coord.info/GLB7R3Z4 The one that got the adverse comment.

http://coord.info/GLB053QT For which I received some good feedback.

http://coord.info/GLB1ZBAW Five days later.

http://coord.info/GLB61E05 Another recent one.

[+The_Incredibles_]

I enjoy reading long logs and I think it's great that you are putting so much effort into your logs....

 

However, since you did ask, cut and paste logs make me nauseous. Everybody in the area, the cache owners and the other cachers, have to read about your glorious day over and over and over...on the cache pages and on their GPSs. Can you imagine if some poor soul is caching in the area after you and goes to read the logs for hints? The only logs they will find will be yours and they won't contain any useful information. The only place I see cut-and-paste logs as being appropriate is on power trails.

 

Specifically, what I like to see is logs which are relevant to the cache in question. I find it kind of bizarre that you would give details about all your cache hunts for the day on each cache page. IMO, if you've found alot of caches in 1 day, you should just stick to writing a sentence or two about each one.

[+Beach_hut]

I must admit I would prefer not to see the same long log over and over again if I was the owner. Perhaps one main long log, and in all of the other logs, a reference to that main long log ("see main log at #1"), plus any pertinent details about that individual cache?

 

But also as a cache owner I don't like to see TFTC over and over again. (And even less in some cases)

 

The way I tend to approach it now is a sentence or two about our day's caching at the start of the log, which is generally copied and pasted throughout each log. I then follow that with a sentence or two about that specific cache. Then finally our auto-generated stats sentence.

 

Kudos to you for making the effort though.

 

PS: I'm looking forward to visiting your part of the world at some stage. Plenty of puzzles and challenge caches I've got my eye on.

Edited June 15, 2013 by Beach_hut

[+thetoxiczone]

On a cache that is series with copy and paste description that tells me nothing about the cache I really can't be bothered writing a long log, unless there is something special about the cache or I wish to pass on information for the next person or the CO. However on caches that the CO made an effort on that cache I try to write more detail about the cache and my experience with it. When reading logs I would skip a log that tells the life history of the cachers day / trip caching as in general there is nothing about the cache I am viewing, in fact they tell me just as much as a TFTC, and as on my GPSr it is not that simple to scroll passed a long log like that looking for more of a hint. Also if you C&P the log over all the caches you found it is just awful to read the same thing every time, think quality not quantity IMHO.

[+wmpastor]

I enjoy reading long logs and I think it's great that you are putting so much effort into your logs....

 

However, since you did ask, cut and paste logs make me nauseous. Everybody in the area, the cache owners and the other cachers, have to read about your glorious day over and over and over...on the cache pages and on their GPSs. Can you imagine if some poor soul is caching in the area after you and goes to read the logs for hints? The only logs they will find will be yours and they won't contain any useful information. The only place I see cut-and-paste logs as being appropriate is on power trails.

 

Specifically, what I like to see is logs which are relevant to the cache in question. I find it kind of bizarre that you would give details about all your cache hunts for the day on each cache page. IMO, if you've found alot of caches in 1 day, you should just stick to writing a sentence or two about each one.

 

I agree with the above - give all the detail you want in a log entry, as long as it's about that specific cache. I enjoy logs that tell a good story - but not if it's about 39 other caches. Post the entire saga on a social media site, maybe.

 

Want to shorten your time spent logging? Write a couple of sentences, max, that give a summary of the whole trip. Cut and paste that to each log - but add something about the search for the specific cache, etc.

[+phillyman]

ditto what The_Incredibles said , for fear of being struck of church micro list LOL ,

 

Well lets say personally where is the detail about the actual cache that the log is for ,

yep I do like longish logs , especially to read but can not write that much myself ,

the logs I like to read best are those written by Mellers ( hope she doesn't mind me name dropping ) and maybe a few others ,

 

But on the other hand I certainly would not discourage your logs as some write absolutely nothing other than TFTC

Well that sounds like sitting on the fence but I would like to see a bit about the day ( concise )

as it does help sometimes if I would like to attempt the same challenges etc.

and a bit about the actual cache , as that is the page that it is posted on

[+halthornhill]

I agree with Bashful.

I tend to write a longer log on the first cache of a series describing the day, the series as a whole and other experiences. I then summarise this longer log and cut and past that into each cache log together with the specifics about each individual one.

I hate the logs that just say TFTC. I even had one that said nothing, completely blank!!

 

Perhaps the complainant would prefer just to have TFTC in future.

Examples of a first in series log:

GC2QEV5

and the subsequent series logs

GC2QEVD

Edited June 15, 2013 by halthornhill

[+Cardinal Red]

There is a very recent thread about log length. You should read it to see the difference between the responses here and there. Every responder there likes a good log. I like a MOSTLY unique log that tells an interesting story. Length alone is not the point. The story is the point. Keep writing until the story is told. What are you accomplishing by repeating the same story 30 to 50 times? Length is only a bonus if it adds to the story. Why would I want to read the exact same story 30 to 50 times? I think your "compromise" suks a little bit. Want to get the logging completed? Write 30 to 50 stories. It might eventually improve your GSAK badge for average length of log? Improve? Is that the word you actually think fits there? Taking "credit" for 30 to 50 stories when you only wrote one? I can't believe I am saying this, but if you've only got one story to tell, write it and 29 to 49 TFTC logs.

[AZcachemeister]

Writing long, descriptive logs is great!

Posting the same long descriptive log on every cache you found that day is not so great.

 

We have a local cacher who used to write up the whole long story of his caching day, and then break it into sections relevant to each of the caches. He would add links at the beginning and end of each log that would take you to the next or previous log in the chain. Thus the log on each cache was unique, yet a part of the whole story. You could click through and read each log in turn if you were so inclined.

 

This would fall pretty much in line with people who write blogs about their caching and, and then post nothing but a link to the blog as their cache log.

[nonaeroterraqueous]

Don't forget that your log is an email to the cache owner. Cut and paste logs are essentially spam. If you treat individual caches like individual people, then you'll be better off. A quick note of thanks is enough, if writing long posts is difficult for you.

[+dprovan]

Yes, please don't do that. Not only is it unbearable, it generates a lot of clutter I have to go through if I'm looking in the log for information about the cache.

 

What I try to do is treat each cache separately, but still while reflecting how it fit into the trip. So the trailhead cache log might talk about the drive and how the cache helped me find parking, for example. Caches along the way sometimes have information about how the trip's going, or how I'm feeling, or why I decided to go there, or why I'm enjoying being there. Typically there are a few caches which are the main targets of my trip, so they get some words about how they encouraged me to take this trip.

 

Instead of one long story repeated over and over, I end up with a story spread out over all the caches in the trip. People reading the logs get a little information that is at least partially relative to the cache they're reading about, while people following in my footsteps can read the whole story.

[+JL_HSTRE]

I agree with writing one big story then splitting it up across your logs. Maybe one or two sentances copy-n-pasted at the beginning.

[+wimseyguy]

Writing long, descriptive logs is great!

Posting the same long descriptive log on every cache you found that day is not so great.

 

We have a local cacher who used to write up the whole long story of his caching day, and then break it into sections relevant to each of the caches. He would add links at the beginning and end of each log that would take you to the next or previous log in the chain. Thus the log on each cache was unique, yet a part of the whole story. You could click through and read each log in turn if you were so inclined.

 

This would fall pretty much in line with people who write blogs about their caching and, and then post nothing but a link to the blog as their cache log.

+1 as a CO I welcome long descriptive logs on my hides that deserve it. But I don't really care about the rest of your caching day. I wouldn't be surprised to learn that the CO who complained owns more than one cache that was found on the caching day in question, and didn't care to see the same text appear in his inbox multiple times.

 

I like the suggestion to link to the previous and following cache log in the unique log. It might be a bit more work for you, but it allows you to tell your story as a full day of caching adventure without giving unwanted details to others.

[+sparklefingers]

as a CO I HATE short logs.

I especially hate TFTC or Easy TFTC or Found. Those logs are just spam in my opinion.

 

Give me a story any day.

[+tozainamboku]

One purpose of the online log is to share your geocaching experiences, but it is not meant to be a substitute for writing a geocaching blog.

 

Some people have asked to be able to link the logs for a day together, so that they, or a friend, can read the logs in order and follow the experience. In fact this can already be done with some difficulty and it requires going back and editing logs to point to the next one.

 

Another purpose of the online log - and perhaps the main purpose - is to provide information about the particular cache both to the cache owner and to other cachers. A long story about what you did all day long tends to have little information that is relevant to the cache owner and to other readers. While you might be using Needs Maintenance logs to provide important information to the cache owner separately, they still may want to see information in the found log that lets them know you enjoyed the cache or if they need to make adjustments that don't really require a maintenance log. Cachers in the field often review the logs for hints in searching for a cache. They aren't going to want to read a long story that probably doesn't have any information about that particular cache.

 

As a cache owner the most satisfying words I see in a a log are "Thank You". Even when those are the only words - even if the cacher uses a text message acronym for these words - they tell me that someone had fun searching for my cache. If someone pasted a long log that didn't even mention my cache and didn't bother to thank anyone for the caches they found, I would consider this just as rude as a blank log.

[Luckless]

I tend to write a little something for each cache. My super long logs are usually about my caching trips where everything went wrong.

This spring I went looking for a cache and it was an easy park and grab. I just couldn't bring myself to write the same old same old thanks for the cache. So I wrote this:

 

WooHoo, XXXX has posted a new geocache, but wait, an impending snow storm is headed this way and it's going to be a big one. Still there's this new geocache out there that I need to find. (Why I don't know, I only know I need to find it.) The heck with the impending storm. They don't call me fearless for nothing.

I put the snow chains on the wheels of my trusty chevy equinox with all wheel drive and whistled for the dogs. "Here Beauregard!" "Here Oliver!" The dogs came running eager to go on a new geocaching adventure after a long winter of cabin fever. I put them in the back of the car and we were off. The snow started to fall as I drove along. It fell harder and harder and I drove on. The wheels slipped and spun on the ice and I drove on. Hail started pelting the windshield and I drove on. Finally everything went white. The snow was coming down so thick I could no longer see the road. Stopping the car I got out and went around to the back where I opened the rear hatch and pulled out the dog sled that I had conveniently stashed in there earlier in the day. I fastened the dogs into their harnesses and hollered "mush". We started down the road with only my GPS to guide us (but not before Waymarking the location of the car). It was slow going for the dogs who sunk down into the snow with each step. The snow laden wind whistled and swirled around us. As I strained to see the road ahead I noticed a group of small children huddled together beside a school bus that had slid off the road into a ditch. I pulled up beside them where I quickly unfastened the dog team from the sled and attached the dog's harnesses to the front of the bus. Then I went around to the back of the bus and began to push. "Mush you dogs!" I yelled. Slowly the bus began to move. I put my back into it and with one great shove got the bus back onto the roadway. "We can't go on," said the bus driver. "We'll have to turn back. Why don't you put your dogs on the bus and I'll drive us all back into town." "No thanks," I replied. "I have a geocache to find." I turned and waved to the children who cheered as we drove off. Only three hundred feet to the cache according to my GPS.

White, everything was white. If there was a geocache here it was buried under several feet of snow. I reached into my geocaching bag and pulled out my handy dandy flame thrower that I keep as standard geocaching equipment in my bag. This will make short work of that snow. Flames lept from the flame thrower melting the snow and igniting a few of the nearby shrubs. After the fire burned out I looked over the charred remains of the area and there it was. "Eureka!" I grabbed the cache and signed the log.

TFTC

and that's exactly the way it happened. Well sort of.

[+frinklabs]

I tend to write a little something for each cache. My super long logs are usually about my caching trips where everything went wrong.

This spring I went looking for a cache and it was an easy park and grab. I just couldn't bring myself to write the same old same old thanks for the cache. So I wrote this:

 

<snip>

 

and that's exactly the way it happened. Well sort of.

 

TL;DR

 

I might have read that, if it had been broken into paragraphs.

[+ShaunEM]

I would suggest finding less caches and enjoying each more. 30 to 50 in a day sounds like a bit of a marathon to me..

 

but then to each his own. I would prefer your cut and paste logs to the TFTC.

 

Shaun

[+Rainbow Spirit]

I use previous logs in the field, to possibly help me get clues about difficult cache hides that I am having trouble finding. Long cut and paste logs that have no direct material about the cache clutter up the limited space I have on my Garmin 20 when I read the log entries, so I get to see less logs.

 

Someone locally was doing long cut and paste logs, so I sent them a PM politely requesting that they limit their logs to the caches in question, since the PM they have shortened their logs, which was nice of them.

Edited June 15, 2013 by Rainbow Spirit

[+RobDJr]

Despite having written many long logs, many of which are tangential to the cache in question, and some of which have little at all to do with the cache, I have never had a complaint. One of my more recent logs came out to ten pages and over three thousand words by the time the dust settled. A little off the deep end, I admit, but no complaints yet.

 

As others have said, I think the issue isn't log length but the cut and paste part. If anything, long cut and paste logs might be worse than tftc logs, especially if many of them are going to the same cache owner. Shorter but unique logs for each cache might be appreciated more, especially if you sprinkle in longer logs for caches that you particularly enjoyed.

[+wmpastor]

I tend to write a little something for each cache. My super long logs are usually about my caching trips where everything went wrong.

This spring I went looking for a cache and it was an easy park and grab. I just couldn't bring myself to write the same old same old thanks for the cache. So I wrote this:

 

WooHoo, XXXX has posted a new geocache, but wait, an impending snow storm is headed this way and it's going to be a big one. Still there's this new geocache out there that I need to find. (Why I don't know, I only know I need to find it.) The heck with the impending storm. They don't call me fearless for nothing.

I put the snow chains on the wheels of my trusty chevy equinox with all wheel drive and whistled for the dogs. "Here Beauregard!" "Here Oliver!" The dogs came running eager to go on a new geocaching adventure after a long winter of cabin fever. I put them in the back of the car and we were off. The snow started to fall as I drove along. It fell harder and harder and I drove on. The wheels slipped and spun on the ice and I drove on. Hail started pelting the windshield and I drove on. Finally everything went white. The snow was coming down so thick I could no longer see the road. Stopping the car I got out and went around to the back where I opened the rear hatch and pulled out the dog sled that I had conveniently stashed in there earlier in the day. I fastened the dogs into their harnesses and hollered "mush". We started down the road with only my GPS to guide us (but not before Waymarking the location of the car). It was slow going for the dogs who sunk down into the snow with each step. The snow laden wind whistled and swirled around us. As I strained to see the road ahead I noticed a group of small children huddled together beside a school bus that had slid off the road into a ditch. I pulled up beside them where I quickly unfastened the dog team from the sled and attached the dog's harnesses to the front of the bus. Then I went around to the back of the bus and began to push. "Mush you dogs!" I yelled. Slowly the bus began to move. I put my back into it and with one great shove got the bus back onto the roadway. "We can't go on," said the bus driver. "We'll have to turn back. Why don't you put your dogs on the bus and I'll drive us all back into town." "No thanks," I replied. "I have a geocache to find." I turned and waved to the children who cheered as we drove off. Only three hundred feet to the cache according to my GPS.

White, everything was white. If there was a geocache here it was buried under several feet of snow. I reached into my geocaching bag and pulled out my handy dandy flame thrower that I keep as standard geocaching equipment in my bag. This will make short work of that snow. Flames lept from the flame thrower melting the snow and igniting a few of the nearby shrubs. After the fire burned out I looked over the charred remains of the area and there it was. "Eureka!" I grabbed the cache and signed the log.

TFTC

and that's exactly the way it happened. Well sort of.

 

Wow, your story is pretty much as good as Jack London's:

DAY HAD BROKEN cold and gray, exceedingly cold and gray, when the [cacher] turned aside from the main Yukon trail and climbed the high earth-bank, where a dim and little-travelled trail led eastward through the fat spruce timberland. It was a steep bank, and he paused for breath at the top, excusing the act to himself by looking at his watch. It was nine o'clock. There was no sun nor hint of sun, though there was not a cloud in the sky. It was a clear day, and yet there seemed an intangible pall over the face of things, a subtle gloom that made the day dark, and that was due to the absence of sun. This fact did not worry the man. He was used to the lack of sun. It had been days since he had seen the sun, and he knew that a few more days must pass before that cheerful orb, due south, would just peep above the sky-line and dip immediately from view....

[+wmpastor]

Despite having written many long logs, many of which are tangential to the cache in question, and some of which have little at all to do with the cache, I have never had a complaint. One of my more recent logs came out to ten pages and over three thousand words by the time the dust settled. A little off the deep end, I admit, but no complaints yet.

 

As others have said, I think the issue isn't log length but the cut and paste part. If anything, long cut and paste logs might be worse than tftc logs, especially if many of them are going to the same cache owner. Shorter but unique logs for each cache might be appreciated more, especially if you sprinkle in longer logs for caches that you particularly enjoyed.

 

A repeated story - if not TOO long - and if it says something about the specific cache it is posted to - and if each posting is to a different CO's cache - is not QUITE as bad as the opposite situation.

[+Ms.Scrabbler]

I am not a fan of cut and paste unless something is added about each individual cache.

What really bothers me is when 3 cachers go out together, each will copy the other with just a change of names. "Went on a cache run from X to Z with 1&2 and found 10 caches." Then you get to read "went on a cache run from X to Z with 1&3 and found 10 caches" etc.

when they find a few of yours you get emails on all finds and get excited ready to read adventures and you get that nonsense.

 

A short "liked the container, tftc" is so much better, more personal if you can't write more.

[+JKMonkey]

long logs usually show how dedicated and appreciative one was towards your cache, how can that be a bad thing?

[+GeoTrekker26]

In a parallel thread I told the originator of that thread how much I liked her long log entry, which is true. In your case I have to agree with the owner that sent you a complaint letter because I actually read the log in question.

 

You have 6 years caching and over 7000 finds so you know what makes a good log. And you know, despite the subject you chose, that it is not long logs that irritated the CO. Rather it is that you wrote one log with a line or two about many caches then pasted that to all the caches you found. Since you weren't honest with us about the real issue, I'll decline to offer comments about your logging etiquette.

[+bjmccacher]

Keep with the long logs! I own over 300 caches and love reading logs without good ones I'd quit hiding so much!

[+Bunya]

Not entirely OT, but I can't see the answer above or in the "Help Center".

I recently got an email from a cacher who had found one of my caches saying he had tried to log a find but it was rejected as "Max Length Reached".

He put his log in the email and logged a shorter version on the cache page.

What is the "Max Length" for a log?

[+Beach_hut]

Not entirely OT, but I can't see the answer above or in the "Help Center".

I recently got an email from a cacher who had found one of my caches saying he had tried to log a find but it was rejected as "Max Length Reached".

He put his log in the email and logged a shorter version on the cache page.

What is the "Max Length" for a log?

 

It's 4000 characters.

 

I have known people to write logs so long they've filled up the log and continued it in a second log, a note.

[+Bunya]

Not entirely OT, but I can't see the answer above or in the "Help Center".

I recently got an email from a cacher who had found one of my caches saying he had tried to log a find but it was rejected as "Max Length Reached".

He put his log in the email and logged a shorter version on the cache page.

What is the "Max Length" for a log?

 

It's 4000 characters.

 

I have known people to write logs so long they've filled up the log and continued it in a second log, a note.

 

Thanks for that.

I assumed that would be the way around the limit, too!

[SwanFire]

My husband and I cache together under the same name...we are new to geocaching and take our cues from logs that we read. Sometimes we've just written "TFTC," especially if the cache was a simple LPC. I had no idea that some COs found that rude. Personally, as a blogger, writer, and craft seller, I prefer ANY feedback to NO feedback. TFTBlogpost or TFTStory or TFTCraft would let me know that someone cared enough to leave a quick note. My effort was seen, noted, and appreciated.

 

Please don't get me wrong...I appreciate the LPC as a quick find for a newbie, especially in the busy urban/suburban environment. But what else can one leave in the log? "The way you hid that pill bottle under the lamp post skirt was so clever"? What exactly would you COs prefer to see in the logs left for your caches? I am honestly asking because I hate the thought that my simple "TFTC" is making some people angry. I'd rather not log my finds if that's the case.

[+BaSHful]

I own well over a hundred caches and consequently see a lot of logs. For each find logged on one of my caches I get exactly one email. Now whether the content of that email is interesting or boring, short or long, or identical to the previous email, it takes just one key stroke to delete it.

[+bjohio]

Admittedly, my logs tend to be on the short side. I can't stand typing on my cell phone. But, I tried to make up for that on find 700 and 701.

 

The day started with 692 finds. It was overcast on this Nation's 145th Memorial Day. The plan was to make GC3N45K "That dam cache #1" my 700th find. If my search proved fruitless, I would move on to GC3R19Z "That Dam Cache #2". After finishing a delicious lunch prepared by my wife, I set out to Fremont to reach #699.

With the air heavy with moisture, I set out to avenge a DNF from a previous outing. As I arrived at GC4ABXW "Tindall Bridge 2", my mind was flooding with horrific memories of the sight of my motorcycle laying on it's side in the gravel after the side stand slipped in the stones the last time I was here. Perhaps this event led to my DNF. Today was a new day and I made short order of this previous misadventure. Six caches and one DNF later, I had finally arrived at the elusive #699. At this point, it was time for dinner. After a satisfying meal prepared by my wonderful wife, I set out to find "That Dam Cache (#1)".

 

Studying several aerial and topographical maps revealed the most prudent approach to be from the East side of the cache. Even though an approach from the East was ill-advised due to muggle issues, I had to take my chances due to the foreboding weather conditions and my lack of suitable gear to fight the raging rapids that lied before me. I parked as close as I could to ground zero. Much to my relief, there was not a muggle insight. I made a final check of all the gear I would need on this journey. Two gel pens, iPhone 5 in a Ziplock bag, rain hat, overalls, gloves, and knee-high rubber boots completed the ensemble. A preliminary survey of the area several days prior uncovered a fairly safe and direct route to GZ. I placed the cell phone baggie in my mouth and carefully made my way across the moving currents. The stones were thick with deep green moss that made each step perilous and fraught with danger. It was starting to sprinkle. With my arms extended for balance, I reached the archipelago miraculously with nary a drop of water in my shoe. As I set foot upon the island, I could feel the crunch of sand and seashells below my feet. The area was lush with all types of vegetation. The copious amounts of poison ivy made the search even more treacherous. I moved South down the island as I started my search not exactly sure what kind of container to expect. I knew that it would have to survive savage weather conditions. I came upon numerous fallen trees, their bark was stripped clean from the millions of gallons of water that have flown down this ancient river. Moving to the highest fallen tree would give me the best view of the area. My strategy worked as I quickly spotted the prize. Before opening the cache, I made a mental note of the ingenious method the cache owner used to keep the cache in place during times of high water levels. I opened the cache and noticed the log sheet stuck to the side, inside the container. This couldn't be good… After dumping a half a teaspoon of water out of the container, I pulled the soaked log sheet out. At that point I had realized, much to my dismay, that I had left all of my spare log sheets and baggies back in my car. I made my best attempts to remove as much moisture from the log sheet by pressing it against my my overalls. Past experience has taught me that gel pens do write fairly well on a wet log sheet if you can get the ink flowing first. For each pen stroke, I drew a line on my overalls and then put a stroke on the log sheet while the ink was still fresh. After completing the log, I reassembled the cache, put away my blue gel pen and started to make my way to shore. The sprinkles turned into a steady rain as I retraced my steps back to my vehicle. Time to move on to GC3R19Z "That Dam Cache #2"…

 

Thanks for making find #700 so memorable. Favorite awarded for a wonderful location.

 

And log 701

 

The now steady rain was reminiscent of our Nation's fallen's heros on this somber Memorial Day. I had just completed GC3N45K "That dam cache #1" as my 700th milestone cache. Having learned my lessens from cache #1, I felt it prudent to prepare a spare log sheet and baggie before setting out for cache #2. With the weather conditions taking a turn for the worst, I wasted no time in making my way to GZ. As with the previous cache, I placed my baggie-encased cell phone in my mouth along with the spare log sheet. With my hands now free for balance and stability, I followed an established trail to the river. The trail gave rise to an open mud bed. With each step, my feet sank several inches deep into the thick gelatinous ooze. Moving slowly through the sludge, my feet finally met the rushing water. After assessing several potential routes, I began to step across the moss-covered stones. Even though the cascading water made my footing unsure, it did help wash away the sizable amounts of mud that had accumulated on my knee-high boots. As with the previous cache, the vegetation was thick and varied. Poison ivy, with it's venomous oils, seemed to be everywhere. Due to the steady rain and thick cloud cover, locating ground zero was laborious. My GPS was putting the cache about 30 feet West right in the middle of the rapids. I knew that placing a cache on the bedrock in the rapids was highly unlikely and attributed it to bouncing. Turning South, I immediately came into an immense mass of fallen trees, branches, and (sadly) trash. The assemblage of refuse was at least 6 feet high and over 40 feet wide. If the cache was under this jumble of debris, it was certainly destroyed. I fashioned a walking stick and climbed the mound. Poking through the rubble yielded little progress. Climbing to ground level, I began to search the surrounding area - nothing. Due to inaccurate GPS readings, I speculated that the cache was located further North on another smaller island that was located approximately 40 feet away. However, it became apparent that the coordinates would have to be way off for the cache to be here. Having found the cache owner's other cache coordinates to be very reliable, I abandoned the search in this area. Moving again back to the South, I began to think outside of the box. It was then, through the pouring rain, I saw the prize. As I approached the cache and extended my hand, I realized that, much to my dismay, that the cache was beyond my reach. I was concerned that a single misstep could incapacitate me and then I would be left for dead on this God forsaken region. What to do? A tool… Yes, I needed a tool. I quickly scavenged the island for an object that would allow me access to the booty. Due to the voluminous rubbish that lied about, finding something to make a tool out of was not an issue. After a few adjustments to the tool, I acclimated my body position to the surroundings to reach the cache. Then it happened, I fell. The rain-soaked environment against my slick rubber boots made me loose my footing and I fell hard against my shin. Furthermore, I proceeded to break the tool I had fashioned just moments ago. After collecting myself, I set about finding materials for another tool. With my second tool in hand, I went about getting my body into position to reach the cache. Success!!! Now, with my body in the most awkward of positions, I placed in my gloved left hand, the tool, container, lid and baggie. I grabbed my black gel pen and signed the perfectly dry log sheet. I didn't need my spare log and baggie after all. Carefully, I reassembled the container and placed it back in the state that I had first found it. Wasting no time, I made a bee-line for the shore as the rain was heavy and unrelenting. Discovering a shorter path to the shore, the journey to my vehicle was swift. Thanks for making find #701 so memorable.

 

Favorite awarded for a neat location and very cleaver hide.

[Clan Riffster]

It's 4000 characters.

That's a wall I smack into on a regular basis.

 

my simple "TFTC" is making some people angry.

I doubt it makes people angry. At least, not a lot of people. Something I learned about this game long ago is, no matter what you do, you are going to agitate someone. You could drop Krugerrands as swag and somebody would complain about it. When a cacher posts "TFTC", it's not really an insult, though my brain tends to translate it into "Your cache sucks". It just means that, either the cache was so mundane that the finder could not come up with anything other than an acronym, or that the finder is too busy to be bothered with communicating anything more specific to the owner. They gotta rush off and find another soggy log film can. Why should they waste time out of their busy day typing more than 4 letters, just to thank someone who spent hours, sometimes even months, creating the cache they just found.

 

Log what comes from your heart.

If that ends up being 4 paragraphs, great. The owner will appreciate it.

If that ends up being only 4 letters, that's kewl too.

 

I own well over a hundred caches and consequently see a lot of logs. For each find logged on one of my caches I get exactly one email. Now whether the content of that email is interesting or boring, short or long, or identical to the previous email, it takes just one key stroke to delete it.

Whooda thunkit?

If asked yesterday if someone could possibly compare a long, thoughtful, relevant log, to a "TFTC" log, and see them as being equal, in any way, I would have questioned either their sanity, their honesty or their intellect. Thank you for showing me the error of my ways. There really is at least one way in which they are the same.

[+Amberel]

Hi Bernard,

 

Late on this one as I've been away all weekend, but it looks like I agree with the majority here.

 

Yes, by all means write a comprehensive log for each cache, but only stuff which is pertinent to THAT cache, not the whole day's caching experience repeated ad nauseum for every single one, and NEVER cut and paste. As someone who frequently follows soon after you on a sequence of Church Micros, scrolling past your logs on an Oregon to get to the next one is an unmitigated pain.

 

TBH, I really can't see any advantage to anyone in regurgitating irrelevant (to that cache) material over and over again.

 

You did ask for honesty .

 

Rgds, Andy

[team tisri]

In recent weeks I have changed the nature of the logs I write which has prompted one cache owner to take me to task and ask me to change (shorten) the log I wrote. I have also had feedback from another cache owner who enjoyed reading about my experiences.

 

I tend (mostly) to cache one day a week and typically find 30 to 50 caches in that day. The practice I have recently adopted is to write a comprehensive account for the whole day (400 to 600 words) and then copy and paste it into every log. If there is a major issue with any particular cache I will raise a separate "Needs Maintenance" log for it. I see this as a compromise between having something (hopefully) interesting to say and actually getting the logging completed. And, yes, it might eventually improve my GSAK badge for average length of log.

 

I welcome some honest feedback on this subject. I suspect there might be a range of views.....

 

If it helps, these are some of my recent logs:-

http://coord.info/GLB7R3Z4 The one that got the adverse comment.

http://coord.info/GLB053QT For which I received some good feedback.

http://coord.info/GLB1ZBAW Five days later.

http://coord.info/GLB61E05 Another recent one.

 

I really don't know why you'd write about one cache while logging another cache, it seems to just cover all the caches with lots of words when most of the words aren't relevant. To my way of thinking you might as well describe how well you slept, what you had for breakfast and the precise details of how you got from your house to the first cache and from each cache to the next cache.

 

It's good to read about peoples' experiences of a cache, especially when I'm looking for it myself, but to read a detailed assessment of their entire day's caching against every cache they find seems pointless not to mention annoying if you're trying to scroll through an essay when using a GPS in the field.

[+lamoracke]

I do enjoy long logs but would admit, if the exact same long log was just merely copied and pasted into every cache, it would get old. Now, if I had a power trail, then I would expect to get whatever I got into logs as there is no way to distinguish cache 2 vs cache 112 so whatever kind of pish posh you get in a log you kinda deserve.

 

Am part of a few puzzle series and I admit, its annoying when folks copy and paste excellent puzzle and the same message into every one of them. You found 40 puzzles in a day and said the same thing on every one of them, how do I really believe you that you thought that of mine? However, I suppose if you said enjoyed this puzzle series on the whole and thought they were fun puzzles to do, then it would be okay but not as cool as a unique message.

 

So, I think its great to do a long log, but its even better to say something unique on every cache one does that day and if you can't, just say something. A relative copy and paste of your adventure is probably better than TFTC, but if you say the same thing on every cache like "excellent puzzle" in your copy and paste, won't believe it personally.

 

Anyway, this post is a ramble, sorry!

Edited June 16, 2013 by lamoracke

[+thetoxiczone]

If asked yesterday if someone could possibly compare a long, thoughtful, relevant log, to a "TFTC" log, and see them as being equal, in any way, I would have questioned either their sanity, their honesty or their intellect. Thank you for showing me the error of my ways. There really is at least one way in which they are the same.

 

A 400 word essay about the persons day caching that basically says I found 40 odd caches with my mates it was a nice day and I enjoyed the walk and does not say anything about the cache in question actually says your cache was so unmemorable I could not be bothered to say anything about it but I will waffle on about the cows in the field 10 miles away and how I had a laugh with my mates etc etc. So total content relevant to that cache is a blank log or if the log writer actually ended it with Thank You, you have a TFTC padded with 398 words of irrelevant waffle. This is why I feel you can compare most of the really long logs to TFTC because that is all they are saying if that. Just because you write 400 word does not necessarily make the log better than a 4 letter TFTC, in fact they are a long winded way of saying "your cache sucked so much I don't remember which one it was out all the ones I found, oh by the way aren't I great for finding them all", my brains translation. If you wish to write about your day get a blog, and post your TFTC and use the text as a link to the blog at least that way every other cacher after you does not have to scroll past, oh hang on you filled the space, yours is the only log they get on their device. Maybe I will have to start posting logs with 5 paragraphs of Lorem ipsum to up my log size

[+rjb43nh]

I write terse logs.

[SwanFire]

 

When a cacher posts "TFTC", it's not really an insult, though my brain tends to translate it into "Your cache sucks". It just means that, either the cache was so mundane that the finder could not come up with anything other than an acronym, or that the finder is too busy to be bothered with communicating anything more specific to the owner. They gotta rush off and find another soggy log film can. Why should they waste time out of their busy day typing more than 4 letters, just to thank someone who spent hours, sometimes even months, creating the cache they just found.

 

Log what comes from your heart.

If that ends up being 4 paragraphs, great. The owner will appreciate it.

If that ends up being only 4 letters, that's kewl too.

 

When I post "TFTC!" that's exactly what I mean...Thanks for the cache! I don't mean the cache sucks or is too mundane, or that I'm unable to think in anything other than an acronym, or that I'm too busy to be bothered. I can't help that your brain translates it and assigns another meaning. As a newbie I saw it in other logs, read the acronym in the site list of definitions, and thought it was accepted practice. I don't always have a story to tell. However, now that I know that some people don't like it, I'll attempt to do better.

 

Thanks for the honest feedback.

[+Markwell]

Back in the day when I was doing my first long run of caches in a single day (August of 2011, 8 caches, over 143 round trip driving miles), I posted a lengthy log on each of those wonderful caches. At the first cache log, I indicated that it was a full day of caching. At the end of each log, I posted a link to the next cache, which started off by saying "This is a continuation from my log on this cache and the day's journey started here" (with links).

 

That way, each log stood on its own, and was descriptive to the owner (and others) regarding the experience of finding that particular cache. If someone wanted to read the whole story, they could start at the beginning, but they didn't have to read the same whole story for each.

 

Doing that for 50 caches may seem tedious, but if the caches each deserve their own significant log, then do so. If the cache wasn't any more memorable than "thanks for the cache", then so be it. It's a happy balance between essentially spamming cache owners, and writing something significant enough to tell your story and thank the owner for placing the cache.

[+funkymunkyzone]

As a CO of quite a few caches, I welcome your long story of the whole day and I don't mind if you copy and paste it to each find. I'd prefer if there were a few sentences in there that relate to each cache, but I'm smart enough to recognise it's the same story and not read subsequent logs that come through the same. Anything is better then "TFTC" or "."

[+Harry Dolphin]

Cut and paste log are BORING. Whether it be "Out caching with ABCD, EFG & HIJK. Thanks for the caches." BORING. Or: "This is what we did today. Same log for 87 caches." BORING! The longer the cut and paste, the worse. If you cannot tell the CO what you remember about his/her cache, then don't.

I may have problems with the logs for the 186 caches on the local trail system. But I try. Cut and paste is BORING! You can do better.

[+wmpastor]

I write terse logs.

TY

[+wmpastor]

If asked yesterday if someone could possibly compare a long, thoughtful, relevant log, to a "TFTC" log, and see them as being equal, in any way, I would have questioned either their sanity, their honesty or their intellect. Thank you for showing me the error of my ways. There really is at least one way in which they are the same.

 

A 400 word essay about the persons day caching that basically says I found 40 odd caches with my mates it was a nice day and I enjoyed the walk and does not say anything about the cache in question actually says your cache was so unmemorable I could not be bothered to say anything about it but I will waffle on about the cows in the field 10 miles away and how I had a laugh with my mates etc etc. So total content relevant to that cache is a blank log or if the log writer actually ended it with Thank You, you have a TFTC padded with 398 words of irrelevant waffle. This is why I feel you can compare most of the really long logs to TFTC because that is all they are saying if that. Just because you write 400 word does not necessarily make the log better than a 4 letter TFTC, in fact they are a long winded way of saying "your cache sucked so much I don't remember which one it was out all the ones I found, oh by the way aren't I great for finding them all", my brains translation. If you wish to write about your day get a blog, and post your TFTC and use the text as a link to the blog at least that way every other cacher after you does not have to scroll past, oh hang on you filled the space, yours is the only log they get on their device. Maybe I will have to start posting logs with 5 paragraphs of Lorem ipsum to up my log size

Maybe some people use caches like background music. *pausing while that sinks in* In other words, the big event is being out with their friends and the caches are a pleasant bonus. Other times someone may be really gung-ho about the caching (and write more cache-specific stuff). Also, I wouldn't expect an essay from someone who finds 20 caches in a day. I'm happy someone visited my cache and a great essay is nice, but a short acknowledgement is fine, too. I'm not going to sit and judge cachers' writing like a high school English teacher! I usually find only one or two caches on a given day, so I've got time to write a bit more.

[+funkymunkyzone]

Wow, some of the really strong negative opinions being expressed here surprise me - not being critical of anyone's opinions, it's just surprising me, and I'm learning something!

[+hukilaulau]

I agree with the majority who say, "Stop it!"

I think of it this way: What's worse than a short, pointless cut and paste log? A LONG, pointless cut and paste log!

I'm glad I had good role models when I was first starting. Even the most prolific cachers in my area wrote unique logs for every cache they found. I've tried to follow that example with the 3500+ caches I've found over 8 years. (I know, some folks do that many in a weekend now.) If it were allowed by GS I would delete any cut and paste log on one of my caches...

[+FunnyNose]

A LONG, pointless cut and paste log!

 

Yup that is the worse. Even more so then the beating of the chest for a FTF.

[+sparklefingers]

My husband and I cache together under the same name...we are new to geocaching and take our cues from logs that we read. Sometimes we've just written "TFTC," especially if the cache was a simple LPC. I had no idea that some COs found that rude. Personally, as a blogger, writer, and craft seller, I prefer ANY feedback to NO feedback. TFTBlogpost or TFTStory or TFTCraft would let me know that someone cared enough to leave a quick note. My effort was seen, noted, and appreciated.

 

Please don't get me wrong...I appreciate the LPC as a quick find for a newbie, especially in the busy urban/suburban environment. But what else can one leave in the log? "The way you hid that pill bottle under the lamp post skirt was so clever"? What exactly would you COs prefer to see in the logs left for your caches? I am honestly asking because I hate the thought that my simple "TFTC" is making some people angry. I'd rather not log my finds if that's the case.

 

on caches that there isn't much to say it's understandable

I just like to see if they come up against any trouble like muggles or they couldn't see it even though it was right in front of them. or that they took the long way to the cache.

 

On caches that are in nice areas i expect a little more then found or tftc.

[Aushiker]

Another downvote for cut and paste logs ... pretty much agree with what has been said before about why they are not fun ... much prefer a shorter but personal log; even better still one that helps me find a cache that has got the better of me .

 

I am curious but about the GSAK badge ... hadn't heard of those.

 

Andrew

[+cerberus1]

Not sure that BadgeGen considered people would use cut/paste logs when they created "The Author" badges for log length.

If separate, uniquely different logs, awesome job.

50 of the same cut/paste, cheesey way to go about it.

I guess like everything else, someone looking to bilk the system will figure out how.