Jump to content

Joe_L

+Premium Members
  • Posts

    126
  • Joined

  • Last visited

Posts posted by Joe_L

  1. I did something like that.  I used a match container (the type for camping) and attached a magnet with a glob of two-part epoxy glue.  The magnets were from a hardware store. 
     

    The cache was sheltered and held up well.  The magnet wasn’t strong enough for the flood waters, but that’s another story. 

    • Upvote 1
    • Helpful 1
  2. On 1/17/2024 at 6:10 PM, qqnonrev said:

    I wait a few years and then use a copy tag (sometimes come with trackable), or a DupleBug or something like it (blank tag to write the number on), or anything I can write the number on (wood coins, etc).  Then I re-release it. 

     

    Plus there is always the chance it will reappear.  That is why I wait several years.  One of ours reappeared after three years missing if I remember.

    But it is your number, so play it as you like.

    I had a similar experience.  In 2018, I retrieved a proxy TB that had been placed in the cache more than two years before.  By that time, the TBO had already released proxy 2.0, so the TBO told me to just hold onto the proxy that I found.  In 2023, the TBO concluded that proxy 2.0 was missing and asked me to release the old proxy that I still had into the wild.  (Side note: a cacher who found this TB in 2015 or 2016 later found the proxy TB that I re-released in 2023.)

    • Helpful 1
  3. The picture size restriction is bad.  Yesterday, I came across a cache with a container problem.  I made a temporary fix.  I tried to message a before and after photo to the CO, but they were just over the limit.  
     

    I was going to email them to them CO, but I used a quick work-around.  I use a Hotmail account so I emailed the photos to myself.  Right before it Sends, it asks what size the attachments should be (Actual, large, medium, and small).  I sent them medium then uploaded the smaller photos to my phone.  Then from there, I added them to a Message to the. CO. 

    • Helpful 4
  4. Years ago I posted a Needs Archived on a cache that I knew was gone. It was a magnetic key holder on a guide rail, and the highway department removed the rail as part of the bridge replacement. The reviewer changed it to a Needs Maintenance using text that was similar to the original post. A month or so later, after no action by the CO, it was archived. The text in the original post looks neutral to me.  Just keep posting NAs as needed. 

  5. 1, 3 & 4 - I rarely check the TB contents of caches before I go out.  So it’s always a surprise. Generally, I’ll retrieve any TB I find, just to keep it moving.  When I get home and find out the mission (like if it wants to go some specific place), I’ll do what I can, especially if I have a trip out of town coming up. Other than that, I drop it as soon as I can. 
    2. I have no idea. 
    5. I try to drop TBs as soon as I can.  On occasions, I’ve held onto a few TBs much longer than typical either because of extended periods between caching, waiting for a trip, absence of caches of suitable size, or in one case, trying to help a TB on its mission. 

  6. When I’ve geocached while on business trips, it’s always been at the destination. Maybe a short drive from the hotel.  
     

    I’ve had occasional long drives, and I’ve considered stopping along the way for geocaches, like in a park or some other interesting location.   The issue was never how long it would take, but rather, what might go wrong: injury, car doesn’t start, minor accident.  Then I would be faced with the question from a boss: “What were you doing there? That’s not on the way to the job.” 

    • Upvote 1
  7. Are you certain that the person who took the cache is the cacher you suspect?  (How good is the video quality?)

     

    A member of the congregation may have taken it without knowing that it was allowed to be there.  Or they asked the wrong person about it.  And the gave it to the wrong person.  (If permission was granted by, say, the pastor, the pastor might not have mentioned it to the secretary or council.)
     

    Does it make any sense that the cacher you suspect would steal your cache? Have they done things like this before?

     

    • Funny 1
  8. On 3/19/2023 at 11:49 AM, kunarion said:

    When did we agree on "Four Weeks"?  Many of my TBs have the specific request that you may pick it up and place it into a cache, or don't take it at all.  No "weeks" mentioned. 

    Sorry about that.  I didn't look at the Help Center before posting which says to place it in another cache 2 to 3 weeks after picking one up.  Bad memory.

     

    There is also nuance to the terms used about tracking that I didn't appreciate.  But in the end, considering the popularity of iPhones in the US, the tag's position will probably be conveyed to the tag owner's phone.  Per the graphics on the AirTag website, the tag's location and address are identified on a map.

     

    In the TB part of the game, once a TB is released into the wild, the only knowledge that a TO has about the TB is the cache that it is in or the cacher who has the TB.  And that applies to the expectations of the cachers who pick up the TB.  Obtaining a home address without consent is just unethical.

    • Upvote 2
  9. I can’t figure out the nested quote function, but a while back a comment was made about why I would think that the AirTag owner would show up.  That is because that is the way AirTags are marketed.  After the lost object is located, the AirTag owner goes to pick it up. 
     

    There was the question of hoarding, but what about forgetfulness or less frequent caching.  Four weeks seems to be the general guideline for dropping a found TB. Would a TB-AirTag owner show up at week five?  Remember, the beep was added to minimize/prevent stalking so the use of AirTags can go beyond finding lost keys.  
     

    I never expected to see an AirTag on a TB, but now I’ll take a closer look.  

     

     

  10. AirTags were made to locate lost or misplaced (and I suppose stolen) possessions, like keys or backpacks.  Presumably, one would go to that location to recover the item.  I would expect the same from a tagged TB - someone will come to my door and confront me about it. 
     

     

    • Upvote 2
  11. Adding an AirTag to a TB strikes me as unethical.  While the intention may have been to track the TB, the result is tracking a person without their consent or knowledge.  Adding an AirTag is also creepy, for the same reason.  Depending on where a person keeps their geocaching kit, the tag could track much more than just their home. And that is bad enough. 
     

    This is what I would do: I would use a hand sledge or hammer to remove the battery so the battery can be properly disposed of.  After determining that the tag is disabled, I would dispose of the tag in the trash.  I would then drop the TB into a difficult cache, but not record the drop. 

    • Upvote 3
    • Surprised 3
  12. I think I recall a similar post long ago about a hide like this.  The cap problems were solved by making an oval shape from a loop or two of heavy wire, like a coat hanger.  The small diameter was a little larger than the inner diameter of the fence post.  A bison tube or similar container was attached to the bottom of the long diameter.  Then the loop was pushed into place inside the post; the wire is springy enough to push against the inner wall and hold the cache in place at the top.  But not so tight that it can’t be pulled out. 

    • Helpful 2
×
×
  • Create New...