Search the Community

We used to get them from a long-time member who claimed to be the FTF king. He'd call the other 2/3rds every time he couldn't find a new cache. Of course never mentioned that he called for a hint, nor say thanks to her after finding it... Finally one time the other 2/3rds gave the phone to me, and I said, "Gee (name wh...), I bet someone will be along to help you shortly..." - And he never did it again... I recently had a couple year member ask about Trackables in email. Gave them all the info, didn't hear back... - And we see questions asked in these forums all the time, and unless you hover over their name to see if they returned, you'd never know. Sometimes I'm tempted to go back a year later and say, "You're welcome...". I feel we just need to realize the world is full of instant gratification gimme pigs. consider the source n forgetaboutit...

I currently have notifications set to send Newly Published alerts via email to my cellphone's SMS email address. (For Cricket users its your cell phone number + @mms.cricketwireless.net). The problem is that the new cache notifications rarely arrive in a timely manner -- usually 30-60 minutes later than ones sent to an actual (Gmail) address. It appears that the body of the outgoing message is altered for the SMS recipient as compared to the email recipient. Pretty sure this has to be happening before it leaves Groundspeak, since it isn't just the same information, but truncated. It has much less information, just a link to the cache page. Annoying, but tolerable. As a test I sent myself an email from my computer to my cellphone's SMS address. It arrived almost instantly. It seems likely the delay is with Groundspeak, not my wireless provider, and reformatting the message is probably part of it. Is Groundspeak the bottleneck? What can be done to get these "emails" to SMS out faster? 30-60 minutes of delay is way too much in a FTF situation. Thanks...

Two Questions.... 1) Wondering if anyone / any group of Geocachers are active in the Tucson area? I am coming to Tucson in March of 2024 with an organization - likely 900 + attendees and probably 60-70 of us are Geocachers from around the US... Thinking about maybe organizing a Geocaching event with maybe a informational meeting and maybe a contest for interested participants ...... Opportunity to maybe "cross promote" memberships" Anybody out there that might be interested in helping ?? Email me at BlueSnowOwl@gmail.com 2) Same rally situation to be in August of 2024 in Redmond Oregon... Wondering same issues - any organization there?, Any interest to jointly "Cross Promote Memberships" ? Email me at BlueSnowOwl@gmail.com

When I log in to geocaching via the website (https://www.geocaching.com/account/signin?returnUrl=%2fplay) and enter email + password, I get this validation email page (see screenshot) for a brief moment before I'm back on the main page, still not logged in. Sometimes, but not always, I also get a blue banner saying something like "Thank you, your account is now activated" back on the main page. I've tested it on Linux with Firefox and Chrome, and on Windows with Opera and Edge, all leading to the same result. However, when I enter my username instead of the email, everything works fine. This being said, the issue is not a disaster but I'd still like to see it fixed since it explicitly says "email or username" on the login page -- or just remove "email or" Thanks in advance for looking into this! Happy hunting, Marty

I received this email this morning and think it could be a scam: I tried looking up the user name and could find nothing. Just wanted to let everyone know to be aware Geocaching <noreply@geocaching.com> To:luvhorses4@yahoo.com Nov 19 at 4:03 AM Good Morning Please, I'm interested in speaking with you about a business deal I desire to actualize with you. Please to further explore this possibility I would like you to contact me via my email address(sazhari.ceo2@gmail.com) to give you a brief description of my field of work and the project idea. Thank You, Mr.Samer Azhari User's Profile: https://coord.info/PRZTME2 ------------------------------------------------------------ This email was sent by Geocaching HQ. 837 N. 34th Street, Suite 300, Seattle, WA 98103 USA © 2019 Groundspeak, Inc. DBA Geocaching. All rights reserved. Terms of Use | Privacy Policy Reply , Reply All or Forward Send 19

Release Notes (Website: New geocache and trackable logging flow) - November 2, 2023 Geocaching HQ is making an ongoing effort to create a consistent player experience across Geocaching.com. Today, we begin releasing a new geocache and trackable logging experience. We will gradually release this new experience to all players over the next few weeks. This latest web release creates a consistent experience across the following aspects: Logging Drafts Creating new geocache logs Editing existing geocache logs Viewing a geocache log Creating new trackable logs Editing existing trackable logs Viewing a trackable log The new logging flow combines the best features of the two legacy logging experiences that exist today, including: It includes a link to the geocache or trackable details page and the respective geocache or trackable owner’s profile page. They open in new tabs. It shows a label indicating the geocache’s status: disabled, archived, unpublished. Players must select log types from a dropdown menu. It includes all available log types depending on cache state and the player’s log history on the respective cache. Once a log type is selected, players will see an updated explanation of the intent behind the selected log type. The Needs Maintenance log type is renamed to Owner attention requested to more accurately reflect the intent behind the log type. The Needs Archived log type is renamed to Reviewer attention requested to more accurately reflect the intent behind the log type. The Log date field now has a “pin” icon to allow players to choose if they want to use today’s date for new logs, or to “pin” a different date. Once a date is pinned, the pinned date is used for all new logs until the player “un-pins” the date or when the browser session expires. The log text input field includes a user-friendly editor for formatting log text with markdown. A modal provides an updated overview of additional formatting options. Log text is now limited to 5000 characters. A log preview section gives an overview of the formatted log. This section is collapsible. It enforces that Favorite points can only be awarded when posting a Found it or Webcam photo taken log. Favorite points can be added or removed by editing an existing log. Image previews now better indicate whether the image is still uploading, is uploaded but has no custom description, or is uploaded and has a custom description. Players can edit uploaded images in a modal by clicking on the image preview links. A trackable inventory section allows players to visit or drop trackables with their cache log. This section is collapsible. We have removed the ability to encrypt logs on cache logs and trackable logs moving forward. Cache logs and trackable logs were not encrypted on the mobile app and very few users used the encryption feature. We have decided to streamline this functionality. We have removed the ability to add a ‘Write Note’ log to unpublished caches. That log type did not automatically archive upon cache publication and private information was occasionally shared. We recommend that players interested in dropping trackables into caches use a reviewer note instead. The cache and trackable log details view also received an overhaul. It remains available via the View Log links from various pages and via direct links. It now features: Additional detail of the current player’s relationships to the cache logs they’re viewing, e.g owned, found, DNFed, etc For cache owners, indication of whether a log had a Favorite point associated with it. Captures a log’s Great story and Helpful votes Updated image gallery utilizing additional space New share log modal Cache and trackable owners are required to provide a reason for deleting others’ logs or images. This reason is shared with the log author or image owner via an automated email. We also updated the image upload functionality for adding images to an existing geocache log, trackable log, and geocache details page. It is now more consistent with images uploaded to a new log, during the Cache Submission Process, and on the Edit Page. It now offers: Drag and drop file upload options Max image size of 5 MB, approved file types are PNG, JPG, and GIF Total number of images per log limited to 20 EXIF data is stripped from uploaded images Image editing in the same interface Adding an image name (limited to 50 characters) Adding an image description (limited to 125 characters) Rotating or flipping an image Please see this Help Center section for more details about logging your finds online. Ari (ari54321) is watching this thread to answer questions whenever possible. Any posts in this thread should relate to features in this release. Comments unrelated to the release may be removed. Please direct unrelated comments to other appropriate threads. Thanks!

I'm either being very dense or not explaining myself properly (either is quite plausible). I cannot fathom how I have made a mistake? I only have a few hides to my name. 1 is achieved which I accept, due to a brief illness and hysterectomy....... Everything I do is on my mobile, I do not know if it's an old or new version. I get email notifications for all my géocaching EXCEPT about enabling the cache itself. If I don't know, then I simply don't know. Therein lies my frustration. Yes I can make a new cache page (the container itself is in situe since replacing it)..... But that is not the point. I've done everything I had been instructed to do.

I was under the impression that I would be sent emails of new caches that are placed in my area. I haven't received any and would like to know when there is a new cache.

It doesn't matter. Really. Anybody can claim FTF on any cache, even if it's been signed 100 times. Does it make them FTF? Of course not. Since FTF isn't a real thing, with no rules, add it to your list of FTFs if you want. So can the person who signed first. You can both claim FTF in yours logs and the world will still turn. Who is FTF on a virtual? The first person to visit the site, or the first person to email answers to the CO, or the first person to post a Found log? FTF on a virtual isn't verifiable either. Same with earthcaches.

The four year old log that was accepted being deleted as revenge would be unfair, I agree. I have two virtual caches that require a photo at GZ. I do everything I can to help the cacher if they log without a photo, including sending them a link to the log, coaching them through uploading a photo, etc. My caches say that I'll delete a log if no photo after 24 hours but I usually wait a week or so and give the cacher every chance I can. Ultimately I just delete the log if they don't communicate back to me. I work to be very communicative with each cacher, even asking one cacher to change a "found it" to a "write note" because they arrived when the park was closed and never made it to GZ, which they did very understandingly. I'll use messenger to communicate with a cacher, I won't write an email to their personal email address. I like the messenger because it keeps the history and I can find it easily. I don't think the OP exclusively requires an email to their email address even though the wording does sound like that, but I would take that wording out personally.

Get the email as an officer saying a Waymark has been submitted, email has a link to the Waymark. Open Waymark via the link and get "This waymark has not been published by the category group yet." and cant publish/decline the Waymark.

You must be way better organised than me then. If I do a day trip away to find a bunch of caches that I preloaded onto my GPSr earlier in the week, I'd be likely in the heat of the moment to lose track of which ones had codewords in them and which didn't, so when I get back home to compose my online logs, well you can guess the rest. The extra effort to remedy that is another day trip away to go back to that cache I found yesterday just to get the codeword I missed first time around. Don't think it won't happen, because that's happened to me more than once with keywords for bonus caches. Not to mention the time I drove all the way to Newcastle to drop a trackable in a cache only to realise when I got there that I forgot to bring the trackable. There's also the overhead for HQ in implementing the codeword in their database, logging flow and cache creation processes. From all accounts there's a lot of old spaghetti code under the hood and messing with it to implement your codewords is likely to break a whole lot of other stuff. It's likely a lot of the long-standing bugs being complained about in the Website section of the forums resulted from some unrelated change elsewhere in the code that had unexpected and inexplicable consequences. I still really don't get what the problem is this is meant to fix. Yes, occasionally I've come across a leaky cache whose log is just a soggy lump of paper mache, but I just do what I can to leave a mark on it, take a photo and log an NM/OAR. That last step is the most important one, as it's what's needed to start the ball rolling and get the problem addressed. But as I said, that's pretty rare, maybe two or three times a year at most. The rest of the time, I just open the cache, pull out the log, sign it, put it all back and I'm on my way with no need to be messing around with taking photos, writing codewords into a pocketbook or whatever. At least until I get home, open my backpack and discover the trackable I meant to drop off is still in there. Now if you could come up with a foolproof fix for that... As for fake logs, as a CO if I see an online log that looks suspicious, I'll firstly go and check the physical log. If there's a matching signature, great, nothing more to do. If not, I'll message the finder and, as diplomatically as possible, ask them what happened. Every time I've had a reply, it''s turned out to be an honest mistake, such as logging the wrong cache. The only times I've had to delete a log were when I didn't get any reply to my original message, my follow-up a week later or my follow-up-follow-up email in case they haven't figured out how to use Message Centre. And that's only happened maybe two or three times in my ten years of being a CO. So I still don't get it. What problem are you trying to fix?

If somebody writes a message including an attached image, the image isn't sent via email anymore. This has worked in the past. It's a disturbing issue, cause sometimes infos to me are sent via images. And by reading the notification email right now I don't even know that an image with important info has been attached.

If you want your Reviewer to check coordinates more than .1 miles away, write an email via their profile page. That workflow is an exception, and is not readily susceptible to automation.

I know I have experienced this in the past and then thought it was fixed at some point but it has started again: I received a couple of email notifications of messages, I reply to them, but then later I notice in the message centre that my replies are not there. So the message centre is making me look like I am ignoring people when I've actually replied to them.

In summary, if I made an email address my primary email address, it no longer displays in the email address drop-down lists on the notification and pocket query pages. I added an email address, validated it, and made it my primary email address through /account/settings/emailpreferences. I thought it odd it didn't show in the pocket query and notification UIs' email address drop-down list boxes. Curious, I set as my primary email an address that has existed in that list for many years. It, too, was removed from at least those two UIs' drop-down list boxes. For testing's sake, I clicked to set as primary each of my other email address. Sure enough, the drop-down lists on those pages are now empty. It does not look as if I can create new pocket queries, but I can still edit and run the ones I have. Due to the nature of the issue, I have not asked anyone else to reproduce it with their accounts. For those wondering if it's a cookie issue, I can prove it's not by bringing up Edge, a browser I do not use and haven't visited the site with before. I logged in using that browser and was unable to see any email addresses listed when I went to add or edit a pocket query. I apologize for waiting more than two months to report this. Honestly, I thought someone else would have reported it by now.

Hello fellow geocachers, I've enjoyed discovering 2 of those mob-caches down under in the state of New South Wales, Australia. Would have loved to create one of these myself. I am sure that many more caches have ulitiised the external linked functionality at geotrailsw.com/mob/. Unfortunately that has now been retired, so I wonder if there are similar functionality out there? It would be a shame to have all these archived, or re-edited as simple caches. I only found out yesterday when one of the unvisited caches (where I was yet to log a find) was edited yesterday (by email notifications) to use a 3rd-party jigsaw puzzle to get the coordinates. A nice interim solution, but would like to have the mobcache option - to bring 2 or more people together. For me, it was a pleasure to meet a geocacher with over 40,000 finds when celebrating my 250th find. Ta, SurdiVisio

I had this problem too and couldn't figure it out. I went to the website settings and made sure the newsletter box was ticked in the Email Preferences section. Still I wasn't receiving newsletters. In the end, I gave up worrying about it. At some point much later, I was looking at the settings in the Official Geocaching app. I clicked on Email Preferences and noticed the newsletter preference was in the off position. I turned it on and voila!!! I now receive newsletters. Perhaps this will solve your newsletter problem???

We have two, I know of, published recently that you have to email an automatic reply email address to get information, I thought that was banned too.

I created the functionality many years ago when lab caches were first coming out, as an example of my own sort of "lab". After getting it vetted by HQ, I released my own as well as functionality for people to create their own. Since then, I have made almost no changes to the code I released, which honestly was just a big old hack. I wrote it on a rainy day while on vacation in the Adirondacks wondering "I wonder if ..." Well it's lasted longer than I expected, but the poor choice of implementation on my side with polling back to the server was causing some issues on the server side off and on. Rather than fix it I decided to retire this fun experiment, about 8 years after I thought I would retire it. Thanks to all who played with it and created their own. After retiring it I found out that there were many more out there than I had expected and I apologize for the sudden retirement. It may come back some day if I decide to rewrite it. I thought after I retired over 4 years ago from a full time software job I would have more time to create and maintain similar projects, but somehow my days are getting filled with other activities! Side note: When I first released this, some random person came across it and wanted to use it for other purposes. They didn't say what the purposes were, but from their email domain I concluded it was for, let's say, anonymous group encounters in the woods. I chuckled, and never responded. I should do a database dump to see if there are any non-geocaching purposes out there.

Unfortunately, I never got my email and I even checked my spam folder. I know I got the email blast on the 19th to my inbox.

Geooh GO does the same as Cachly plus more. Email support for assistance.

I've only ever done one auto-responder virtual and had the same problem. After trying a few things with the CO, we determined that gmail didn't like emails with just an address but no content, and after writing a short novel for the body, it worked. I also have a separate email account for geocaching set up on the same domain as my regular email but identifying me as "barefootjeff" rather than my real name.

Send the answers by message center/email, which the CO ignores. Or send to the auto respond email which gives you a reply "Congratulations, you may fill in your Found It log"

The email address associated with my account is no longer in use and I do not have access to it, so I thought I would update it today. I clicked on 'Add Email' and a box appeared. I typed in my new email address however, when I typed in my password, for security, it said the password was incorrect, despite me only just signing in using it. Anyone else had this? What did you do to work around it? Thanks Pete