Jump to content

MtnGoat50

+Premium Members
  • Posts

    383
  • Joined

  • Last visited

Everything posted by MtnGoat50

  1. MtnGoat50

    Safari

    When I can't access a site from one browser but it works with different one, the first thing I try is to delete cookies for the problem site. I don't have a Mac and only use Safari on my iPad but to delete cookies there go to Settings -> Advanced -> Website Data -> in the search box type geocaching.com -> Edit and delete. I personally avoid removing all cookies, for all sites, because that sometimes causes new problems.
  2. Kind of an old thread and you may have moved on or given up but if you bought City Navigator pre-installed on a micro SD card from Garmin then you can transfer the card from GPS to GPS and it should work. No unlock codes required. Here are a couple of things to look at. Go to the map page on the GPS and click menu. Scroll down and select, "Setup". Are any maps listed? Is the check box under, "Show" checked? Another thing to try is to connect the GPS to a computer with a USB cable. Click the menu button twice and select, "Setup". In the Setup menu select, "Interface". At the top under USB does it say, "Connected"? If it does go down to the bottom and select, "USB Mass Storage". That should open the file manager on your PC and the SD card should show as a USB Drive (#:). In the Garmin folder you should see a map file called, "gmapsupp.img". Anyway that should tell you if there are maps on the SD card and if the GPS can read the card. I always loved my 60CSx, it was one of my favorite units back in the day. I still have it, and would never part with it, but I haven't used it in years.
  3. I do. I want people to find my caches and I'm always happy to help. It's nice to get a "thank you" back but it doesn't always happen. A bit disappointing but not something I worry too much about.
  4. ...and the Grab option is available if the trackable is set as collectable but not in a collection. Again, per my previous post: If a TB is set as collectable AND it is NOT in a collection the options are, Write Note, Grab it, and Discovered it. Which, (I think) is correct. Example: https://coord.info/TB7V68Q
  5. To simplify what I said yesterday. I'm seeing two issues. If a TB is set as NOT collectable, AND is in the hands of another player, the only options are, Write Note, and Discovered it. Which, (I think) is NOT correct. You should be able to also Grab it. Example: https://coord.info/TB61D94 If a TB collectable preference is not set, AND is in the hands of another playler, the only options are, Write Note, and Discovered it. Which, (I think) is NOT correct. You should be able to also Grab it. Example: https://coord.info/TBA05C6 Everything else I tried worked as expected. Again, the workaround is to grab the trackable using the free official app which is functioning correctly. This is definitely a BUG that needs to be fixed.
  6. I was intrigued by the OP and did some testing. Here is what I found using the new logging flow on the site: (Win10, Chrome) If a TB is set as collectable AND is in a collection the options are, Write Note, and Discovered it. Which, (I think) is correct. If a TB is set as collectable AND it is NOT in a collection the options are, Write Note, Grab it, and Discovered it. Which, (I think) is correct. Example: https://coord.info/TB7V68Q If a TB is set as NOT collectable, AND is in the hands of another player, the options are, Write Note, and Discovered it. Which, (I think) is NOT correct. You should be able to also Grab it. Example: https://coord.info/TB61D94 If a TB collectable preference is not set, AND is in the hands of another playler, the options are, Write Note, and Discovered it. Which, (I think) is NOT correct. You should be able to also Grab it. Example: https://coord.info/TBA05C6 If a TB is set as NOT collectable, AND is in a cache, the options are, Write Note, Retrieve from cache, and Discovered it. Which, (I think) is correct. If a TB collectable preference is not set, AND is in a cache, the options are, Write Note, Retrieve from cache and Discovered it. Which, (I think) is correct. The above was tested using Win10 and the Chrome browser. When using the app everything works as expected, with all the correct logging options available, so if you're having trouble logging a TB using a browser and the site try using an app as a workaround until this can be fixed.
  7. It took some searching but these are the sizes I bought based a recommendation from another cacher back in 2016. 2” (standard) bison: E70012-PC, 012 EPDM peroxide cured 0.364” ID x 0.07” CS (minimum order (25 qty.) costs $3 (12 cents each). I think I got 50 and a selection of the other sizes to meet the $9.95 free shipping.) 2.5” bison: E70014-NSF, 014 EPDM peroxide cured 0.489” ID x 0.07” CS Megas: E70135-NSF, 135 EPDM peroxide cured, 1.925” ID x 0.103” CS SCUBA: E70016-PC, 016 EPDM peroxide cured, 0.0618" ID x 0.07" CS You can save some money by skipping the peroxided cured option but my understanding is they hold up better and last longer. I'm not saying you're wrong and I'm sure it varies from region to region but my experience in my area is that the hardware store has a poor selection in geocaching sizes. That and paying $1 for a single (close to) bison sized o-ring made me look elsewhere.
  8. I get my O-rings from The O-Ring Store in Clarkston, Washington. The 2mm X 11mm E70 EPDM 70 Duro Metric O-Rings cost 10 cents each (20 qty. minimum). Their minimum order is $5 and you get free shipping at $10. They have pretty much any size and any material you want. Someone recommended EDPM to me for outdoor use so that's what I bought. I bought a variety of sizes for bison, scuba bison and Mega bison.
  9. It's working fine on my old (almost obsolete) iPhone 6s (and also on my newer iPad pro). I sometimes get the "no caches found" message when I zoom in too close. I assume you've tried zooming out and panning around. My best suggestion would be to reset the filters and try again.
  10. Why don't you post your image here? That should help people understand who is (and isn't) being unreasonable.
  11. I didn't see anything in the post I was responding to about PQs only general site performance and I stand by what I said. If you're having issues with the API and PQs maybe you should start a thread about that. FWIW I haven't had any issues with PQs either so I strongly suspect the problem is at your end.
  12. Are you sure the issue is with Geocaching.com? The site has generally been working fine for me. The few slowdowns I've seen have been acknowledged and addressed quickly.
  13. I'm not a fan. The first TB I created was moved from the cache I placed it in to a TB hotel. I week later it was marked missing and never seen again. I released the copy tag a year later and it did better but the experience soured me on TB hotels.
  14. If it's locked you won't be able to post any log and will get an error saying it's locked. The listing has been locked and is not accepting new log entries. If it's collectable it will say so. Look near the top of the listing under Recently Spotted: If it's collectable it will say, "This is collectable". As others have said, if the owner wants it to travel like a normal trackable they need to edit the trackable and set it as not collectable.
  15. LOL. I could have written that! Skirt lifters are noisy and hateful. Guardrail caches are often in nice locations, usually don't require much stealth and are not NOISY. I've never understood why people lump them together. The last skirt lifter I found was during covid in a deserted office building parking lot. I lifted the skirt, grabbed the container, turned around and here comes the security guard. "What are you doing?" Me, "geocaching". Him, "this is private property." It was a strange conversation. He knew about caching, I think he even knew the cache was there. He let me sign the log and when I asked if I should take it with me or put it back, he let me put it back, but his last words as I left were, "this is private property." FWIW the cache had been placed by someone that worked in the building and at least claimed permission. When I first saw this thread I assumed it was all, "tongue in cheek" joking. When I saw the post above I was like, really? So I checked your profile to see how many you've placed and how it was working out. (nice try though)
  16. Where did this happen? Where was the cacher coming from? I live in the pacific northwest and often (at least before covid) crossed the border to British Columbia. Around here all the Canadian border guards I"ve met know about caching. I even had one recommend caches to find and provide some great local knowledge on how to approach a cache. I also have a couple of good caching friends that work for Canadian customs. That said you never know who you're going to get.
  17. On 3 and 6 you can't specify a city. Only countries, states, and counties (or their local equivalents) are allowed. See Item 10. Source of Criteria which under Not Allowed, says, "Challenges based on geographic areas other than countries, states/provinces, counties (or their local equivalent). Examples: user-defined mapping polygons, latitude/longitude, radius, etc."
  18. That is correct, as Kunarion said, you can't drop a trackable from the TB page, you have to do it from the cache page where you intend it to go. Here is a quote from the Help Center article: Drop and Visit logs Follow these steps to drop a trackable in a geocache or log a visit to a geocache. From a cache page, select Log geocache. Below the text box, select an action for each trackable from your inventory: Drop, leave the trackable in a geocache. Visit, take a trackable to a cache but keep it with you when you leave. If you're still having trouble I can post some screenshots.
  19. Instead of logging from the TB page, post a write note log on the cache page where you’re dropping it and select the TB from your inventory list.
  20. Did select the name from the drop down list or type/paste it in? The search will only work if you select the name from the drop down menu.
  21. That seems like a lot. I suspect your reviewer will ask you for a list of 10 other local qualifiers. See 5. Standard for Criteria in the Help Center which says: "A challenge cache needs to appeal to and be attainable by a reasonable number of cachers. Your reviewer may ask for a list of cachers from your area who qualify." Why 10? I've done 6 loops (366/6) and I'm happy with that but if wanted another goal it would be 11 (where the color on the grid changes) not 10.
  22. You have two lists in your post, both numbered 1 to 6. As was mentioned above the challenge cache guidelines now (since 2016) prohibit time limited challenges such as: 1. 3x3. - within 24 hours (one day) to visit 3 foreign countries and find 3 geo-treasures each. and 5. find 6 different types of geo-treasures in 24 hours. Look at item 9. Time-Limited right at the top under acceptable, "Time-limited caching: as in some number of finds per day, week, month, or year." Also, regarding: 6. Attend an event that has "night cache" attribute. and 6. Attend an event that has "boat required" attribute. Have you considered that to qualify all an event host has to do it add these attributes to their event? The problem with any attribute challenge that they're easily manipulated by other cache owners. In both cases removing the 24 hour time restriction would solve the problem.
  23. I am assuming from your profile picture that the user name you want is GeoDuck92? It looks like the account was created using the app and they never visited the site otherwise. There are no finds, no hides, no profile picture to search for...nothing. I think emailing them or doing anything to remind them of the account is a bad idea. If they log in to the account on the site it will reset the last visited date and if they log a find from the app the account will have a history and I don't think HQ will ever adopt the name over then. If it were me I'd change my Geocaching name to Geoduck_92 which (IMHO) is close enough that most won't notice. Then I'd mark my calendar and at the 5 year mark, assuming no activity, try HQ again.
  24. The first time I crossed the Canadian border to go geocaching (circa 2007) I tried that. After a few of the usual questions the border guy asked if we were geocaching. Of course I admitted we were. He then asked where we were headed and made several recommendations for good caches, along with a great tip on how to approach one of them. It wasn't until he let us go that I realized I was wearing a geocaching logo hat that gave me a way. At least when it comes to the border between Washington state and BC (from me experience) they all know what geocaching is and don't consider it strange or suspicious.
  25. That's something I had forgotten about but now that you mention it, I'm sure you're right. It's only recently that's been possible. Previously all background images were entered as a URL for an image hosted somewhere else. It could be on Geocaching.com or some other site. Yep, I remember that too. That's my fault, I shouldn't have included the "/large/" , which is optional, as part of the URL. On the cache you mention the URL is http://img.geocaching.com/cache/1fb65f38-c275-40dd-8be7-286f866218d1.gif so it's one that was uploaded to a cache page, as opposed to a log. Anything older than around 2021 ( I don't know the exact date) you would have had to have entered a URL. Uploading a background image directly is a new feature and it's no longer possible to enter a URL. (this is something I find inconvenient but I suspect new people find it less confusing) I don't think not on purpose. Some images have been lost in the past but I only remember one instance. From what I'm seeing all the missing backgrounds share the /user/ designation in the URL. It's only a guess but perhaps these were considered expendable and removed. Similar to how we used to be able to see previous avatars and profile pics but can't now...?
×
×
  • Create New...