Jump to content

VAVAPAM

+Premium Members
  • Posts

    407
  • Joined

  • Last visited

Everything posted by VAVAPAM

  1. So do you think it would it fly if the cache were on the book-mobile *at that particular stop*? (We're talking about a very rural area, thus the book-mobile.)
  2. Thank you for your response and insight. Yes, I was imagining a decal - either magnetic or static cling. But to create a cache page, I see your point: Creating one at a stop would make sense. (The depot is at another branch of the library.) Thanks again, TriciaG
  3. This seems a likely place to ask my burning question. Please do redirect me to the proper forum if I'm mistaken in posting it here. I am featuring different branches of a library in a series of caches. One of the branches is a book-mobile. From what I've read on other recent forums about No Multiple Logging when that came out, I imagined, then, that a travel bug would be the way to go with the book-mobile. OR a specific stop that the book-mobile makes regularly. Would you imagine a different solution? Thanks in advance for your help.
  4. I used to believe this but i know and have seen firsthand that it doesn't work. What i like is the opposite of what most others go for these days. The vast majority want quick and easy. A cache that's different or challenging rarely gets a visit. --------------------------------------------------------- First, let me say that I enjoyed Barefoot's descriptive post; it expressed quite a bit of my joy of caching. I guess I am fortunate to live in an area where there are still exceptionally creative and challenging caches. *However*, I also acknowledge that those caches have been around for a while... and I am a relative newcomer to my geo-community. (Yeah, I just made up that term; sue me.) Even in the small community in which I live, I am trying very hard to think up caches that will make people go, "Okay, that was cool," when so many very cool caches were already placed... and found. It's about the joy of the find - whether thinking of it from the finder's perspective, or the CO's imagination of what the finder will experience. We relative new COs are out here. We're out here; we're trying. You guys ahead of us just made it really freaking hard to come up with new ideas. Thank you, sincerely, for that. It is because of those creative caches that I have been able to "think outside the box" and come up with some new ideas. Figuring out how to make them work and where to put them takes a bit of time. And how about making the "numbers people" happy, too, every now and then? As they say, "Variety is the spice of life." Guess I'm saying that you are not alone in the appeal of caches for which you have to work a bit, but let's not completely omit quick n easy - it's hard to start at the top, you know? I do agree with the concept that if you want it to be better, make it better. It's just that it's hard to improve on what's already here - but, by golly, we're working on it.
  5. Update: One last appeal to try the adoption tool, with attention to username, was a success. Thank you for your suggestions.
  6. Very good point, and I thank you for it. Unfortunately the CO has apparently tired of the whole process and ended communication. I will just post NA and move on. Thanks to all for your thoughtful suggestions.
  7. I wanted to know why for a couple of reasons. First, to better prepare myself for a situation that might arise that I hadn't foreseen. Second, I wanted to better understand your reasoning/logic, because mine did not follow yours. So thank you for clarifying both points for me.
  8. deprovan wrote "...it compounds the problem to make someone doing an adoption track down and check a box just to make sure they know they won't be able to do something they weren't planning on doing, anyway." 1)Not sure what you are envisioning, but I meant a simple checkbox - normally checked by a single finger tap or mouse click - just before the Adopt button (which would not be active until checkbox checked). No tracking down; no major ordeal; just one extra tap right there, practically a double-tap on an already very short form. Sorry for not being more clear. 2)I guess I doubt any one's ability to know someone else's plans, unless they tell me. The checkbox tells me they don't mind not logging a find on an adopted cache. If it bothers them, I guess there will be no adoption. No confusion or confounding, 'unstreamlining'. No searching help pages. The rule is right in front of them. Accept and Adopt, or move on. "If they are one of the few COs that ends up with a good reason to log a find sometime later, likely they'll have forgotten all about the checkbox by that time, anyway." 1)This sincerely is not meant to be facetious; chalk it up to my ignorance: What are the reasons for logging a find on your own cache? 2) Ah, but they were warned and it was acknowledged by checking that box.
  9. Thank you, Touchstone. I had not thought of linking to the archived listing. Cool.
  10. Sometime this month, logging your own cache as found will no longer be possible. It is safe to say that. Edited to add the Upcoming Logging Rules. Alrighty, then; thank you for that! Will inability change expectations? Just saying, not sure those would change.
  11. As to the assumption that most would not adopt a cache they'd not previously found: Of course, if the cache has been in need of maintenance with a history of DNFs, often there is no ability to log a find before adoption. I have seen these and thought, "That's such a shame," and considered whether they are in my "maintenance comfort zone", and if they are - if close to my own or my home base - I will consider offering to adopt if it's in a great place or highlights a great feature, facility or service; however, most often the COs have been out of the game for a while and do not respond, though not always. As to the adoption warning: To me, adoption means transfer of *ownership* and therefore logging a find on one's own adopted cache would fall into the category of PLE (poor logging etiquette). On the other hand, I appreciate that not everybody's thought processes are the same. In my case, I would not expect to be able to log it, but perhaps there are others that might wish to do so. I don't think it's safe to assume that some adopters would expect to be unable to log their un-found adopted caches as a new find. I see no harm in such a notice ... perhaps a simple, standard checkbox similar to the ones for creating a cache would do. (Whether you're creating a new cache or simply editing the listing, you still have to check those boxes, so I assume there's no code to search whether you've already indicated that you've read those guidelines before.) So, a simple checkbox statement such as, "I understand that I will not be able to log this as a find after I take ownership of this cache," or something - whether the adopter had found it or not - might indeed serve to give notice and pause to some who might expect to have been able to do so, thereby precluding some disgruntled adopters' complaints. Would it be superfluous? For what I think may be a great number of other geocachers: NO, I really do not think it would be. For me and most who visit the forums: Yes. edit-spelling, sheesh
  12. Noticed a long need for maintenance/DNF in logs and sent message to CO letting them know... and my reluctance to post NA if they were going to check up on it soon. Surprisingly (given their prolonged absence), the CO replied almost immediately that they weren't going to get to it, so NA would have to be ok. I offered to adopt (it's a good location, highlighting a good facility) and included how-to. In a few minutes they responded that they had just completed the process to adopt the cache to me. I have not received the usual notice via email - even after several hours wait - and when I enter the GC# in the adoption tool, it says I haven't been asked to adopt it. Now what? VVP
×
×
  • Create New...