+grrtrainman Posted March 14, 2012 Share Posted March 14, 2012 (edited) Okay, My BAD! A fellow cacher received the same type of logs and I mistakenly assumed there was something amiss after the recent update. My apologies. Edited March 14, 2012 by grrtrainman Link to comment
Keystone Posted March 14, 2012 Share Posted March 14, 2012 Okay, first we get the lousy, worthless maps. Now it appears that finders logs are coming through with some weird letters and numbers. Talk about "FUBAR". The bovine excrement is really hitting the rotary oscillator... Please read the pinned thread for instructions on how to post a proper bug report. Then, edit your post. If you don't wish to edit your post I will be happy to close your thread. Link to comment
+Lil Devil Posted March 14, 2012 Share Posted March 14, 2012 Now it appears that finders logs are coming through with some weird letters and numbers. I'm not seeing this. Are you sure the finder didn't really include those letters and numbers in his/her log? Link to comment
+Lil Devil Posted March 14, 2012 Share Posted March 14, 2012 LOL. It's like I'm clairvoyant or something. Just looked at your three caches that were found today, and sure enough the logs are funny looking. But that's exactly what the finder wrote. If anything is FUBAR it's your attitude. Link to comment
jholly Posted March 14, 2012 Share Posted March 14, 2012 Okay, first we get the lousy, worthless maps. Now it appears that finders logs are coming through with some weird letters and numbers. Talk about "FUBAR". The bovine excrement is really hitting the rotary oscillator... Maps are fine. As to the logs they are not to hard to figure out. Find # - time found - who was there and SB2012 is Spring break 2012. Pretty simple coding. What is ah, er, hmm, euphemism for family unfriendly state is that you did not take any time to decipher what the log was about. Pretty much the blank log with some characters. Link to comment
+Dancing_Duo Posted March 14, 2012 Share Posted March 14, 2012 Just took a look.... "633 - 4:04 PM - DNR + J1 - SB2012" 633 was the # they have found 4:04 PM is the time they found it DNR is part of their username Too close to my bedtime to figure out the "+ J1 - SB2012" (although the 2012 part is probably the year) Link to comment
+Dancing_Duo Posted March 14, 2012 Share Posted March 14, 2012 SB2012 is Spring break 2012 Ok, that makes sense Link to comment
jholly Posted March 14, 2012 Share Posted March 14, 2012 SB2012 is Spring break 2012 Ok, that makes sense Yeah, it popped out when looking at a couple other logs from DNR that was logged today. I was thinking J1 might be a friend. Link to comment
Pup Patrol Posted March 14, 2012 Share Posted March 14, 2012 Pretty easy logs to figure out. IBTStoned B. Link to comment
+ChileHead Posted March 14, 2012 Share Posted March 14, 2012 Pretty easy logs to figure out. But it's much easier to assume the site is "messed" up. Link to comment
+Car54 Posted March 14, 2012 Share Posted March 14, 2012 Just took a look.... "633 - 4:04 PM - DNR + J1 - SB2012" 633 was the # they have found 4:04 PM is the time they found it DNR is part of their username Too close to my bedtime to figure out the "+ J1 - SB2012" (although the 2012 part is probably the year) Based on their user name, I'm guessing J1 is one of the "N3JS", meaning not all 3 J's were along for this find. Just a guess.... Mrs. Car54 Link to comment
+grrtrainman Posted March 14, 2012 Author Share Posted March 14, 2012 Thankfully there are cachers out here that can figure out things this addled brain can't. Thanks Guys! Link to comment
Keystone Posted March 15, 2012 Share Posted March 15, 2012 Closing this thread. Thank you to the OP for realizing the error. Link to comment
Recommended Posts