|
Post by NorthWes on Apr 21, 2009 20:00:04 GMT -9
While we're testing the limits of what pushes our buttons here in Alaska, let's broach this topic...
Suggested protocol for the 'HINT' option - for cache owner, and for cacher.
During a recent visit by the "Alaska Cache'n'Dash" crowd from the Seattle WA area, including Miss Jenn - PR rep for Groundspeak (the geocaching.com folks), and Moun10Bike - now a programmer for Groundspeak, the topic of how the cache owner handles the hint option came up. As we were searching, the visitors turned to decipher the hint. They were quite frustrated to see a hint which read 'No Hint For You', and commented to me about it. Seems the consensus from Groundspeak is the Hint is for a genuine hint - not a poke in the cacher's eye - no matter how funny the cache owner thinks they're being. I twisted my lips at the remark (smirking), and asked 'why so'? Their answer (from their perspective as spokespersons for the game as a whole, played at its kindest and most developed level...) made sense (and kinda humbled me). To summarize: if you don't want to provide a hint, leave it blank; to do anything but provide a genuine hint just irritates folks who don't decipher the hint before the cache hunt, and is a slam on persons (little kids!) who're laboriously deciphering the ROT13 code in the field.
So - what's your thoughts on these two parts of the topic? Here's mine:
1) The HINT option should either be left blank or used for genuine hint OK - I'll buy into this one - I agree with this point of view
2) Do you decipher the HINT before you go afield, or only on the spot if you need it? I'm ruthless - my phone is equipped with Geocache Navigator (thanks to akwhodini for turning me on to that blackberry app!), and I use it to read the hint. Further, I always decipher the hint when I'm reading cache listings online as part of my planning process for the cache hunt.
If you're a cache owner I'm particularly interested in your thoughts on item 1; as far as item 2, I think it's perfectly normal to read the hint in advance - or not.
|
|
FLYRFN
Silver Cacher
Posts: 180
|
Post by FLYRFN on Apr 21, 2009 20:09:44 GMT -9
My opinion: A hint should be a real HINT.
|
|
|
Post by ladybugkids on Apr 22, 2009 6:22:30 GMT -9
I've been recently seeing cache reviewer notes on new cache pages when a "useless hint" is posted, suggesting that the cache owner delete the text. The reviewers haven't been consistently posting their comments. 1. Don't want to give a helpful hint? Leave the hint box blank and bump up the difficulty of the cache 0.5 or 1.0 stars. The "Hints/Spoiler Info" box on the cache submittal form states "If you don't have a hint, leave it blank." 2. It's a mixed bag for me on when I decipher the hint. Sometimes I don't look at the hints at all. Sometimes, especially when doing research for backcountry caches, I'll look at the hint ahead of time to better anticipate whether I'll need special equipment for a cache retrieval. Sometimes when powercaching with a group or time is short, I'll decode the hint on the spot to have as much information available as possible for a quick find. There's a great Useless Hints thread over in the gc.com forums that makes for some fun reading.
|
|
laddd
Bronze Cacher
Posts: 12
|
Post by laddd on Apr 22, 2009 8:04:54 GMT -9
"Don't want to give a helpful hint? Leave the hint box blank and bump up the difficulty of the cache 0.5 or 1.0 stars."
I agree with this. And I like the comment about developmental level- I know several people who cache with their little kids and would avoid a more difficult cache OR prepare their child for it first.
"If you don't have a hint, leave it blank. " Seems like it should be self-evident but, good to say anyway.
And as far as the second question goes, being new to my GPS I haven't actually figured out how to decipher hints in the field- hmmmmm- or, in fact, several other things that my Garmin probably does.
Frankly, I take my GPS with me when we're out walking and just stop by caches if we're near one. This has, on several occasions, had me unable to find a cache, which I later find out when I look online, no one else has been able to find either- for months. Or the cache is in need of maintenance and we probably wouldn't have wanted to slog it out anyways.
My future philosophy will probably look something like this: 1) caches I can easily return to I won't look at the hints before I go. With the caveat that once I figure out how to access hints in the field this will probably cause me a lot less future frustration LOL. 2) any epic cache journey I'll look before I go.
Right now I'm okay with just walking around.
|
|