Jump to content

justintim1999

+Premium Members
  • Posts

    2427
  • Joined

  • Last visited

Posts posted by justintim1999

  1. 8 minutes ago, barefootjeff said:

     

    A lot of the caches I do don't get found very often, so any previous logs may well have been prior to the cache going missing. The tree cache that's now a flood barrier was last logged a year before my visit, while the one with the spoiler photo had been found a month earlier but other evidence around GZ (freshly painted graffiti and dropped chip packets) suggested the muggling had happened just days before my visit.

     

    It's much the same with my own hides. The one that recently had the DNF log just saying "DNF" was last logged in 2022 and has had just one find since, so anyone wanting me to do a check won't have much in the way of past logs to go by. A lot can happen between searches, particularly with all the wild weather we've been having in recent years.

    I had one in the burnt out hole of a large tree.   Someone posted a dnf so I went out to find the tree had finally fallen.  I'm sure the cache was there under the rubble somewhere.   Although the tree was about 4 foot around and looked to be solid as a rock, I'm glad no one was in the area when it came down.   Wonder if it made a sound?

    • Surprised 1
  2. 14 hours ago, barefootjeff said:

    But regardless, you don't have to be 100% sure it's missing to log an Owner Attention Requested, you just have to be sufficiently convinced to warrant asking the CO to please do a check.

    Kind of like guilty beyond a reasonable doubt.    All kidding aside, I'm sure that in most cases asking a CO to check up on their cache is warranted based on previous logs.  You would hope the cache owner is reading the same logs you are and would voluntarily take a look.    Not sure if we're going off into the weeds again but i think if you use the logs as intended and take a 2nd look before posting a NM or NA, things will work out just fine. 

  3. 42 minutes ago, Goldenwattle said:

    Agree with the first two. The third one though depends on how many DNFs before you and the cache rating. If you are the first DNF, that's all that should be made, unless it's obvious the cache is missing, such as a landslide at GZ. Even a tree or other structure missing doesn't necessarily mean the cache is missing. Examples; I came to a chopped down tree, but the tree loppers had found the cache and left it by the tree stump. Another, a footbridge had been removed (the cache had been hidden in the structure underneath), but the workmen had found the cache and it was sitting unharmed under a nearby tree. I did message the CO about the bridge cache. But in neither of those cases was the cache missing.

    If there had already been several DNFs, and depending on the cache difficulty rating, I would make the DNF and then a NM. Often when I have done this I have been annoyed that others before me hadn't done this already, but many are scared to even do a DNF, until someone else has, so this is not surprising.

     

    A NA needs to be held off for at least a month after the DNFs and the NM have continued to be ignored by the CO, and no word from them.

     

     

     

     

     

    I have yet to DNF a cache I was 100% sure was missing.    Had many DNFs  I've returned to find within a minute with a big ole slap on the head wondering how I could have missed it the first time.  If we're talking about a cache hidden in a tree in the middle of a desert that has 3 DNFs,  then I'll play along.  I think those situations are few and far between.      Let's be clear.  No one should be scared to post any log that fits the situation.  But If you're going to assume, let's just hope you assume correctly.     

    • Upvote 1
    • Surprised 1
  4. If I were a cacher and didn't find the final for any reason....DNF noting where along the way I was stopped.   I wouldn't consider the Owner's maintenance log as I wouldn't post an OM for a missing trackable but I would mention it in the DNF or in a separate note.

     

    If I were the owner.... I'd see two finds (I assume the OM on the missing trackable was a find) and one DNF.    Everyone's maintenance runs are different, but I wouldn't be moving up my schedule any time soon for one DNF.    I also wouldn't be removing the trackable until I could confirm it was missing.   I would take note of the Cachers experience though.   I know that some people think that a series like the one you described absolves them of actually having to check up on them from time to time.   I guess that's something you have to be willing to do if you're going to place a series like that.  I would think an owner of a cache like that would appreciate the accurate use of logs...especially the owner's maintenance one. 

  5. Found the cache = Found log

    Found the cache & it needs maintenance = Found & Needs maintenance logs

    Didn't find the cache = Did not find log

     

    Needs archived is the only subjective log choice and should only be used with care.  

     

    If you post the correct logs eventually the cache will be flagged, and a reviewer will get involved to resolve the issue one way or the other.      

    • Upvote 4
  6. I have two musette bags.  One set up for finding caches and one for cache maintenance.    The find it bag has basic stuff. 

     

    tweezers, multitool, pens, pencils, note pad, first aid kit, solar battery bank, a couple of magnets, a bit of bank line, compas (out of habit), swag.   Room for a water bottle or two. 

     

    I should upgrade the maintenance bag to something bigger.   Lots more stuff involved.    

  7. In the found log a month ago they noted the cache needed maintenance.   The previous 15 logs and the one after indicated the cache was fine.   Knowing the hide the only issue would be a full log which I replaced in March.   Glad they didn't post a needs maintenance log based on the condition of the cache when they actually found it.  

  8. 5 hours ago, cerberus1 said:

     

    We used to get a lot of very late (some years) "backlogged" Found Its.  Most were kids finally opening their own account.   :)

    We told parents for years that it's easy to keep track which kid found what by simply marking a Trackable in their name, and Drop/Retrieve (and now just "visit") each cache they were with you on.

    If/when that kid wants to cache later (later doesn't have a timeframe...) they simply copy caches from that Trackable's history. 

    Some would even be long-archived...

    If you feel this person's log might be "bogus", just send an email.  We don't know your or his story....

    There's a cacher near me that caches in a few states (PA and AZ mostly), and is on various committees in the area.  A real busy person.

    I can't recall when they logged a cache the day or two after finding it...   

     

    This cacher has 314 finds so it could be someone catching up on their own account.   in 10 years, this is the first time I've encountered this.   Looked odd at first but it seems possible it's legit.   Thanks 

  9. Received an email today regarding a found log posted to one of my caches.   The log is dated 5/24/2020.   The cache has been archived since September of 2021.   

     

    This individual logged two other caches today.    One was part of a series which included the cache listed above (also archived).   The other was logged as found 6/18/2023 from a series 25 miles away.  

     

    Has anyone experienced people who log finds years after they've been found?    Do you think these logs are bogus? 

     

    Thanks   

  10. 1 hour ago, niraD said:

    If the CHS system can't deal with the way people actually post logs, then the CHS system needs to be fixed. Most people will not change the way they post logs to suit the CHS system's limitations.

    That's your opinion and I respect it.   My opinion still stands.  I don't expect the CHS to be going any where soon.  In that case I choose to change how I log to support what GS is trying to do. 

     

    I'm sure the OP can view both sides of the issue and decide what the best course of action will be. 

     

     

    • Upvote 2
    • Funny 3
  11. 5 hours ago, barefootjeff said:

     

    To the best of my knowledge, my cache was the only one affected but they didn't find many caches before they lost interest and most of the others were urban hides where doing that sort of thing would likely draw undue attention. There were three in the photo but only one logged a find so perhaps one of the muggle mates went back after the cacher had moved on. Also another local cacher recognised one of the three as someone he knew from his pre-caching muggle days so I suspect there might be more to this than I'm privy to and which I really don't want to become embroiled in.

    I feel ya.    You can except an animal or mother nature destroying one of your caches but I never understood why a reasoning brain would think doing something like that was somehow a good thing.  Just picture your cache on fire and Yogi Bear coming along to put it out.;)   

  12. On 7/20/2021 at 6:29 PM, barefootjeff said:

     

    Unless animals can operate zippers, I'm pretty sure it wasn't an animal. A newbie PM cacher messaged me that they'd been looking for two hours for the cache and needed more hints, so I replied with a photo showing a prominent feature close to GZ. There was no reply, or either a found or DNF log, so I went around to check on the cache to make sure it was still good (which it was) and see if there was a signature in the logbook (there wasn't). A week later they messaged me again, wanting more and more hints. One of their messages included a photo of them (there were three, late teens or early twenties, one with a cigarette in his mouth) standing in front of that prominent feature and wanting to know whether they had to look left or right. I replied with "Down" and a few minutes later they said they'd found it. Not convinced they were likely to put it back correctly, I went back round there again the next day, only to find the stash note lying out on the ground and part of the novelty spider container poking out of its hiding place, with the logbook sitting on top of it and the pencil under it.

     

    20200817_100324.jpg.ab7626e7f311e6634d1ec193cff6139e.jpg

     

    When I pulled the spider out and unzipped the pouch in its belly to put the logbook back in, I discovered it contained a pale yellow fluid. I suppose I should be glad they had the decency not to leave the logbook in it.

     

    So I suppose it's possible a muggle might have done it between visits, but that seems pretty unlikely as the cache is well concealed and is somewhere muggles are unlikely to be wandering by (its terrain rating is 3.5 and takes quite a bit of bush-bashing and rock scrambling to reach). Anyway, their premium membership lapsed soon afterwards and they haven't made any finds since late last year so hopefully they've found another passtime to annoy.

    Was the cache well concealed after this find?   Did you reach out and ask them about it? 

     

    If they were truly bad cachers I'd bet you'd notice a few NM logs after some of their other finds.   Seems odd to go through all that trouble to find a cache just to vandalize it.      I tend not to jump to conclusions on things like this but to be honest I've never had something like this happen to me.   Most of what I see looks like inexperience or simple mistakes.     I think most people who understand the game have more respect than that......but I'm sure there are exceptions.       

  13. 2 minutes ago, thebruce0 said:

    But in this context, you're saying it's okay for cache owners and finders to just shrug off things people do that negatively affect people's experiences, to not "obsess" over them.  I think it's naive to think the hobby can survive if such actions can run amok.  I think the middle ground, which I'm advocating, is that promoting good practices that make the hobby better, and discouraging practices that make the hobby worse for people, is not "obsessing", but healthy community strategy for the sake of the community. Obsessing is a whole different level that can make things worse, just as those who "cheat". On the other end, doing nothing at all can also make things worse as the hobby simply degrades.

    Healthy promotion of practices that benefit the hobby and community is the best course of action. At least some mix of that and apathy :P a net positive.

    No... what I said is I'm all for playing the game right but I'm not going to put a bunch of time and effort policing those who choose not to.   I take care of my caches and when finding a cache I'll post the appropriate logs according to the situation.  The rest I leave up to the reviewers to handle. 

     

    The only way to encourage "good practices" is through example.   The only way to discourage "bad practices" is through logs.  

     

    What I won't do is get upset or discouraged over something I have very little control over.    

  14. 4 minutes ago, thebruce0 said:

    Yep, obsessing is unhealthy and unhelpful.  But healthy promotion of what benefits the community should be encouraged.  If everyone were to simply take a hands off approach and shrug off everything, that was spell the end of the hobby. Enforcement falls in the hands of TPTB, but as a community we can promote the good and discourage the bad - without obsessing over enforcement.

    I think most people who hid and find caches do so because they want to not because they have to.   I also think that the vast majority of them are responsible and try to to the right things.   For those reasons I don't think a hands off approach would spell the end of the hobby.

     

    I'm all for playing the game right,  I just don't let those who choose not to effect my enjoyment of it.   

    • Helpful 1
  15. Same as you.   If it's all about the smiley, a caching streak or some sort of challenge I can see how one would be "effected".    I pretty much know the solid cache owners in my area so If I'm involved in something like that I'll try and choose a cache I'm relatively confident will be there and in good shape.

     

    I enjoy the find as much as the next person but it's not the primary reason I cache so false find logs, wet caches and missing travel bugs don't bother me all that much.     

  16. Just had a discovered log on a travel bug I've had in my possession for over three years,  even though it states on the TB page "No virtual logs please".  

     

    No in depth investigating needed on this one.  I just deleted the log and moved on.

     

    Obsessing over cheaters just ruins the game for me.   I have better things to do with my time than police the Geocaching community.   In my opinion you can't legislate morality and trying to do so is a huge waste of time.        

  17. On 4/27/2021 at 5:40 PM, barefootjeff said:

     

    I think I'd classify the one who urinated in my cache as "bad". Even an inexperienced cacher ought to realise that's not how you sign the log.

    Are you sure it was a fellow Geocacher?    Could it have been a muggle or an animal? 

     

    As for me I still can't think of any bad cachers.  

    • Funny 1
  18. 2 hours ago, ByronForestPreserve said:

    Well, the problem was that they replaced the hide but didn't remove the old container, then deleted my log when I found their geotrash. 

    My comment was responding more to deleting a find because of the "I didn't have a pen" thing.    

     

    In your case I don't agree with having your find deleted.     I also think one smiley isn't worth the time and effort. 

     

     

    • Funny 1
  19. 3 hours ago, ByronForestPreserve said:

    My area had a caching family banned several years ago. They put out very difficult caches and policed the heck out of them. I found a relatively easy one and got a message a couple days later: "We didn't see your name on the log and we think you didn't find it, we're going to remove your log." I replied by describing the find in detail, to which they said, "Oh, that was the OLD container. You didn't find the new one."  I sometimes wondered if micromanaging their cache logs was their full-time job. 

     

    I'm also convinced, but cannot prove, that they had bogus accounts to "find" caches that got NM or NA logs to make it look like the cache was in good shape. Actually, maybe someone proved it and that's why they were banned....

    I have no problem with someone following the guidelines to a T.    If you are a cache owner I'm sure you've had your share of "Didn't sign the log.   Forgot a pen".  I can't remember the last time I've forgotten a pen but if for some reason I didn't sign the log I wouldn't expect the cache owner to let it slide.   They have every right to delete my find and I'd double check my bag to make sure I had a couple of pens with me next time.      

     

    I consider myself a responsible cache owner but I can count on one finger the number of finds I've deleted. 

     

    I guess I'm just to darn trusting.  I could never be a judge (or reviewer).....everyone would be innocent.   

     

     

    • Funny 1
  20. 1 hour ago, frostengel said:

     

    Geocachers are people so whatever makes people bad makes geocachers bad, too: bad manner when talking to you, don't caring for others stuff (e. g. caches by other owners), ..... long list!

     

    Or do you want to know what makes a cacher bad as cachers especially? I would make two lists here:

     

    1) Be a bad finder by ...

    - ... getting mystery and multi finals from online data bases or cheating in any other way.

    - ... not taking care for caches and stages (for example when putting the logbook back).

    - ... using copy and paste logs for each cache.

    In general: ... putting your own statistics (that's everything, of coruse) higher then the demands of the owners forgetting that these are the people who take time and money to just create th caches.

     

    2) Be a bad hider by ...

    - ... hiding uninteresting caches, mainly micro traditional caches in boring places.

    - ... not being any creative with their own caches (hide and listing). Look in your hidden profile and you see an example: seven caches which are absolutely the same.

    - ... being resistant to good advice (you don't have to to everything others suggest but think about it) especially when they have done something wrong.

    - ... don't maintaining their caches though several finds have told about a problem.

     

    Both:

    - ... don't caring about environment, animals, people nearby, ...

     

    And there is much more but without exactly knowing what's your purpose with the question - posts like yours are what makes a bad forum user - that should be enough by now.

    You posted the topic and haven't replied at all - that's not how communication in the forum works. :-(

     

    Jochen

    I just can't get all worked up about all that.   All you can do about most of it is log your NM and move on.   The only thing I can really control is my own geocaches.   Lead by example and sooner or later people with notice.  

     

    I think you'd be better off if you'd stop obsessing about what others are doing (or not doing)  and concentrate on enjoying the experience.

     

    People choose to play the game all kinds of ways.   Why not just let them do that?     

    • Helpful 1
    • Love 1
×
×
  • Create New...