Search the Community

Would posting a Write Note to the cache page saying that you have tried other means to contact the CO and would like to talk with the CO about adopting the cache? Just spitballing here...

I'm sorry you feel this way. Geocaching events are not equivalent to "meetings" at all, at least in my neck of the woods! And the variety of events means you can choose what you want to do! We gather to have pizza, and socialize - very informal, and we have learned a lot about our fellow geocachers, met some very nice folks, and made many connections that have helped us along in our retirement hobby. We meet to clean up a park (CITO), have coffee in the morning, sip wine on a patio, play with gadget caches, work on puzzles, all are unique and different. We too, began geocaching when hubby retired (2017). We greatly enjoy attending events and getting out to meet others. Of course, we like meeting others on the road as well, but I wouldn't ever lump all events together as "meetings" akin to work meetings....I think you are missing a big piece of what geocaching is about! We've come to realize that we are people with a different kind of hobby that not everyone understands or "gets" - and to be able to meet with like minded folks and talk about experiences is one of the things we enjoy most about geocaching! Maybe try a local event, just once, just for this one souvenir. You may be surprised!

Usually Keystone will step in and say "hey everyone, let's keep this on topic, we're supposed to be talking about <topic>". But there's been minimal talk about geocache of the week and lots of talk about adopting caches from CO's who no longer participate. Hi back. I never did return to NYC to find that cache near the the ferry.

We appreciate the passion that some players have for benchmarking. And thanks @thebruce0for trying to come up with ideas to try to help. However, at this time we would like to focus our resources on geocaching and Adventure Lab. To implement any of these ideas, we would have to slow progress on other projects that are more important to our core products. As a recent example, we have a team who made key improvements to the Pocket Query API and is working to fix a couple bugs resulting from that update. We believe those who are passionate about benchmarking can still participate in a variety of ways. Many of the contributors in this thread have pointed out opportunities where you can still participate, such as through Waymarking or by directly reporting benchmarks to the NGS. You don't have to stop finding benchmarks. As a reminder, in the last 365 days, about 2,500 players have logged a benchmark. This represents ca. 0.13% of players who have logged a find during that same period. We know that some players are disappointed about our decision to retire benchmarking. But the numbers give us a clear indication that this is not a critical part of our offerings.

Thank you all for sharing your passionate and candid feedback with us. Please continue to share your feedback with us in the comments. Let me address some of the points that were made so far: I can understand that it comes as a surprise because historically Geocaching HQ hasn't completely retired many site features or pieces of game content. Hence, when we do, it appears more significant than it might be for other organizations which do so much more regularly. I can however assure you that this decisions was far from random: Benchmarking was identified as a dependency for another project that is currently in-progress and nearing completion. We aren't quite ready to share more details about it, yet, which is why it wasn't mentioned in the pre-release notes. At the time, a decision had to be made to shift course and accommodate this new dependency or to not do so and retire benchmarks. The cost to accommodate benchmarking far exceeded the cost of retiring it and so after reviewing usage data and ongoing maintenance costs, the respective decision was made. Please see further context below. Before making this decision, we carefully reviewed information regarding benchmark finds and the number of distinct players who found benchmarks in the past years. Both have been on a steady decline since 2010 and even more significantly since 2015. Most recently in the last 365 days, only ca. 2500 distinct players have logged a benchmark. This represents ca. 0.13% of players who have logged a find during that same period. Puzzles will remain solvable if the puzzle requires finding information on the actual benchmark plaque or the associated information. Those are still available by visiting the location or via research on the NGS website. Puzzles relying on finding information in benchmark logs on geocaching.com will indeed become unsolvable and should be archived. I can assure you though that this affects a very small number of caches. The fact that you never noticed how broken it actually was if anything is a testament to the hard work of HQ's engineers who frankly don't receive a lot of love here. As correctly noted by @essap2, maintaining these old pages requires significant resources. These resources can then not be spend on other improvements, including new exciting features and long standing community requests. To the point made by @niraD, Geocaching HQ is making an ongoing effort to "get the house in order". This requires updating several old code bases. While I understand that this is hard to hear, not all of them are salvageable or worth the considerable work to migrate them to a new environment. I understand the disappointment that comes with a beloved part of the game going away. While I understand that it isn't completely the same, I encourage you and everybody else to check out the Waymarking.com benchmark categories for U.S. benchmarks and Canadian benchmarks. Alternatively, you can obtain the data from the NGS directly. There are also different apps out there dedicated to benchmarking for both Android & iOS. Scraping the website constitutes a violation of the terms of use and you risk a suspension of your account if you opt to proceed this way. If you want to make this information available to others, please go the route proposed by @chaosmanor and contact the NGS directly. They'll also be able to provide you with a much more up-to-date file. The geocaching benchmarks database hasn't been updated for quite some time. I understand that it is disappointing. Unfortunately, this is an all-or-nothing situation and nothing isn't an option in this case. You and all others who feels strongly about their benchmark logs and photos have some time to save them for yourself. Starting with the List of your benchmark logs on https://www.geocaching.com/my/logs.aspx?s=3 is a good starting point. I understand the frustration and agree that there are lots of opportunities in the geocaching world and how other platforms could be integrated in it. Unfortunately, with a finite amount of resources we have to be selective in which ones we pursue. At this point benchmarking isn't one of them due to its locally restricted nature when the game as a whole becomes more and more global.

Agreed. Such as Hint: red. Real example. You only get the hint on the hard to find cache when you remove the cover and see the red cache. Doh!!!!. Annoying. Want people to talk about your cache with annoyance, and that reflects badly on the CO and their intelligence, or lack of, thinking that was a hint? Give a non-hint like that!

I didn't even own a smartphone 10yrs ago. So I didn't use an app at all, but I remember talk about phone apps back then. I don't care about the premium caches right now and yeah, I know they've been around since I was last a premium member. What irritates me the most is the inability to filter caches on the website and I'm pretty sure that functionality was available to basic members in the past. Just to be able to display caches on the map that were harder, or larger containers (so I could filter out all the lamppost micros, or micros-in-the-woods that I don't like searching for) so I could download the .gpx for them to transfer to my garmin. but without paying, I have to just click on stuff until I find something that meets my criteria. that sort of thing is going to get old really fast.

Is there a souvenir for 365 / 366 days of caching ?

I am very interested in this project. I have always been an advocate for Wherigo and I personally have built a lot of them and have helped many others build them as well. While I am not a coder I can test, build, tear apart, and am willing to do whatever necessary to help bring some advancement to this issue. Also, I do have the ability and the platform to get the word out through our Podcast Network (Geocache Talk). this could be handy if we need more testers or builders or just want some feedback. I am very interested in this project. I have always been an advocate for Wherigo and I personally have built a lot of them and have helped many others build them as well. While I am not a coder I can test, build, tear apart, and am willing to do whatever necessary to help bring some advancement to this issue. Also, I do have the ability and the platform to get the word out through our Podcast Network (Geocache Talk). this could be handy if we need more testers or builders or just want some feedback. Memfis Mafia

I've been happy with my Nokia 6.1. When it's time to upgrade it, I'll probably get another Nokia. They have Android smartphones at various price points, but they're all designed with value and future Android upgrades/updates in mind. That depends on your service plan. I've been happy with Metro on their lowest level plan. My wife uses TracFone, and each year, when she buys another 365 days of service, she gets more minutes of call time and GB of data than she uses in a year. I have no idea what Verizon's plans look like now. That depends on the app you use. Even Groundspeak's app can preload PQs, although other apps have made that easier. But the API-based apps that I used to use were no longer being maintained, and Groundspeak changed the API in ways that were not backwards compatible, so those apps stopped working. One of these days, I'll find another API-based app that that I like, but for now I've be getting by with Groundspeak's app.

Next Monday all being well (if the Americans don't send any more hurricanes our way ) I'll fill in calendar day 365/366, just under 22 months since starting out. I imagine I'll be far from the only cacher then waiting patiently for 29th February 2016 to come around?

Yes, and it leads to a little bit more of a mystery... Went out when I could, and started digging around. I did, in fact, find the station that the carsonite post was for! .. But it was NOT for the station that I had expected - it's for an Azimuth mark for a triangulation station, a 3/4 mile away at the top of a mesa. Station has not been recovered since 1958, so the carsonite post is newer than that. Neither the station that is destroyed there, or the description of the AZ mark make references to each other. I have plans on getting the station on the mesa - I need to talk to the ranch owner first. And will need to get a metal detector, and start sweeping the general area for possible hits.

Have you tried to talk with the leader

This post is being written as a community member, not as a moderator or Groundspeak volunteer. My opinions are my own. Urwigo is likely the most fleshed-out of the third-party builders, followed by Earwigo. We don't have a more fleshed-out builder because Groundspeak hasn't really done anything to encourage the community. I haven't heard anything to the contrary about reviewers being advised not to publish Wherigo geocaches that specifically cite the (free) third-party builder app used to create the cartridge (yet cache listings involving certain other services that have a premium tier are allowed). Internally, the community has talked about revising the Wherigo specification, which has also likely had an impact upon development (but without the community's hosting the listing service, specification changes wouldn't be able to be listed on Wherigo.com, which would then certainly cause Wherigo geocache listings not to be published). I had created a second version of Kit, but never published it because I'd then have to finish the rest of the site's design and I tired myself out. My job over the past five to six years has willingly and eagerly been interested in consuming all free time I would like to put into developing software. I figure it's better to put the time into my job and have what I create be used than attempt to continue Wherigo development--especially the cartridge listing service--and chance it likely never really being used. Besides, recreating it with a modern API, Blazor front end, and microservices in the back end would increase the cost I pay to host Kit and the Wherigo Foundation site. I already pay a not insignificant cost every year to host everything. It would be sad to double it or more with a microservices-based infrastructure if it's not going to go anywhere. In early February, I requested a meeting be set up with me, but I haven't heard anything since. I wanted to talk about Wherigo's future and what active role Groundspeak could play in the community. I myself am not that good in keeping a group of people engaged in a pursuit. I'd need one or two other people to play off of. I'm willing to give it one more shot if we can keep an active and engaged team. I guess for me, the largest obstacles are lack of encouragement, lack of anyone who might want to assist with developing a professional web-based builder, and Groundspeak's seemingly-apathetic stance on the matter.

Let's talk, you pick the subject. You will get our two cents worth... and take it with a grain of salt... oops, should have said: Open topic about Waymarking.

Sorry for the vague title, I didn't know how else to address this. So, I know there's a lot of talk about Geocaching and YouTube, and there's been a sort of agreement as far as I can tell that as long as you don't really post spoilers about a cache and it's specific location, for the most part all is well. Well, there's a pair of YouTubers whom I occasionally watch called MoreJStu that make all kinds of vlog type videos, several of which have recently included geocaching. At first I had no problem with what they were posting. I figured if it got some more people interested in our hobby, that's great! But then they posted this video today: https://www.youtube.com/watch?v=FEub1s5AXUI There is so much misinformation in it about geocaching that I was nearly yelling at my screen. I think it's okay that they're wanting to share a geocache with the fans, there's nothing wrong with that. Except they show where they pack snacks into the cache and encourage others to come out and trade snacks too. Not only that, but they practically bury the cache. It's one thing to hide it with some foliage, but they literally made a hole to put it in. I'm not here to get them in trouble or anything, but I just hate the fact that they're demonstrating behavior against the rules of Geocaching to their 2.7 million subscribers... They also make it kind of known that in more than one video they usually don't trade swag, only take it. If you look on the comments on their vids, you constantly see things like "Ya'll inspired me to start geocaching!" and "Because of ya'll I'm building a geocache fort!". Which is great, except the majority of their followers are young kids who I know aren't going to read any of the rules before going out and geocaching, which will just create more problems... What are ya'll's thoughts?

1-7 sind die Richtlinien, die restlichen Punkte Beispiele Der angesprochene Punkt 9: Maintaining a finds streak, at least one find per day, up to 365 days. Finding some number of caches per month, provided the number is cumulative over all years. Example: 100 finds in Januarys. Finding some number of caches per day of week, provided the number is cumulative over all years. Example: 100 finds on Mondays. Das sind Beispiele die der Reviewer genehmigen würde, da steht nichts davon, dass die zeitlich befristet sein müssen, oder dass du die alle erfüllen musst. Übersetzung von oben: Eine Serie erstellen, mindestens ein Fund pro Tag, bis zu 365 Tage. Finden einer bestimmten Anzahl von Caches pro Monat, vorausgesetzt, die Anzahl ist über alle Jahre kumuliert. Beispiel: 100 Funde im Januar. Finden einer bestimmten Anzahl von Caches pro Wochentag, vorausgesetzt, die Anzahl ist über alle Jahre kumuliert. Beispiel: 100 Funde montags.

No, it's the same issue that I described previously. Comcast is now throttling Weekly Mailer messages we attempt to send by deferment, so our server keeps retrying until the message is accepted or expired. In this case, it took ~4 days. Here are the logs: Sep 30 13:40:36 signal2 postfix/error[18592]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=0.1, delays=0.1/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta34.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 14:21:55 signal2 postfix/error[27076]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=2478, delays=2478/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Sep 30 15:15:28 signal2 postfix/error[26069]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=5692, delays=5692/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta10.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 17:31:19 signal2 postfix/error[21426]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=13842, delays=13842/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta19.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 21:50:24 signal2 postfix/error[21488]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=29388, delays=29388/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta25.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 02:20:11 signal2 postfix/error[17888]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=45575, delays=45575/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta25.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 06:50:08 signal2 postfix/error[14401]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=61771, delays=61767/4.3/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta28.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 11:20:24 signal2 postfix/error[10233]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=77988, delays=77967/21/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta09.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 15:50:18 signal2 postfix/error[5719]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=94181, delays=94167/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta30.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 20:20:06 signal2 postfix/error[1014]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=110369, delays=110367/2.6/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta29.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 00:50:09 signal2 postfix/error[29149]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=126572, delays=126572/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta12.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 05:20:20 signal2 postfix/error[24714]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=142783, delays=142764/19/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta32.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 09:50:20 signal2 postfix/error[20450]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=158983, delays=158965/19/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta27.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 14:20:05 signal2 postfix/error[15686]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=175169, delays=175165/3.9/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta02.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 18:50:05 signal2 postfix/error[11213]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=191369, delays=191365/4/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta21.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 23:20:32 signal2 postfix/error[5842]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=207596, delays=207564/32/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta26.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 03:50:18 signal2 postfix/error[1119]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=223782, delays=223765/17/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta12.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 08:20:09 signal2 postfix/error[28593]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=239973, delays=239966/7/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta38.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 12:50:08 signal2 postfix/error[23322]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=256172, delays=256167/4.6/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta17.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 17:20:18 signal2 postfix/error[18820]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=272382, delays=272367/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta08.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 21:50:19 signal2 postfix/smtp[13687]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=mx1.comcast.net[68.87.26.147]:25, delay=288583, delays=288567/15/0.3/0, dsn=4.0.0, status=deferred (host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta18.westchester.pa.mail.comcast.net comcast Try again later) Oct 4 02:20:12 signal2 postfix/smtp[8287]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=mx1.comcast.net[68.87.26.147]:25, delay=304776, delays=304768/6.3/0.3/0.7, dsn=2.0.0, status=sent (250 2.0.0 YxL81m02s3RP4Bm0QxL95o mail accepted for delivery) And I still don't get one. Yours is still in queue for delivery: Sep 30 14:23:56 signal2 postfix/error[17402]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=0.1, delays=0.1/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Sep 30 17:01:53 signal2 postfix/error[20668]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=9478, delays=9478/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta14.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 19:48:30 signal2 postfix/error[10666]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=19475, delays=19475/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta06.emeryville.ca.mail.comcast.net comcast Try again later) Sep 30 23:50:09 signal2 postfix/error[26238]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=33974, delays=33974/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta21.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 04:20:05 signal2 postfix/error[22530]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=50169, delays=50169/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 08:50:11 signal2 postfix/error[18967]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=66376, delays=66367/8.7/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta35.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 13:20:23 signal2 postfix/error[14592]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=82587, delays=82569/18/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta17.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 17:50:19 signal2 postfix/error[10261]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=98784, delays=98769/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta18.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 22:20:17 signal2 postfix/error[5594]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=114981, delays=114969/13/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta06.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 02:50:19 signal2 postfix/error[1345]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=131184, delays=131171/12/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta30.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 07:20:30 signal2 postfix/error[29898]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=147394, delays=147371/23/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta37.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 11:50:23 signal2 postfix/error[25103]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=163587, delays=163571/17/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta13.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 16:20:22 signal2 postfix/error[20394]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=179787, delays=179771/16/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.COMCAST.NET[68.87.26.147] refused to talk to me: 421 imta38.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 20:50:21 signal2 postfix/error[15742]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=195986, delays=195971/14/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta15.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 01:20:22 signal2 postfix/error[10582]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=212186, delays=212171/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta20.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 05:50:22 signal2 postfix/error[5603]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=228386, delays=228370/16/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 10:20:31 signal2 postfix/error[832]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=244595, delays=244572/23/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta15.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 14:50:28 signal2 postfix/error[28274]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=260792, delays=260773/19/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta23.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 19:20:24 signal2 postfix/error[23125]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=276989, delays=276974/14/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta24.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 23:50:26 signal2 postfix/error[18230]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=293191, delays=293174/16/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta03.emeryville.ca.mail.comcast.net comcast Try again later) Oct 4 04:20:30 signal2 postfix/error[12972]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=309394, delays=309376/18/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta01.westchester.pa.mail.comcast.net comcast Try again later) Oct 4 08:50:36 signal2 postfix/error[8163]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=325600, delays=325579/22/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta16.westchester.pa.mail.comcast.net comcast Try again later) Oct 4 13:20:35 signal2 postfix/error[2929]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=341800, delays=341778/22/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta24.westchester.pa.mail.comcast.net comcast Try again later)

We...don't do that here. That's not so much unholy as heretic. We don't talk about Mm-mm, no, no, no! We don't talk about Mm-mm! Grew to live in fear of Mm-mm being mentioned here Newbies post, thread is toast, moderators near I associate Mm-mm with the sound of locking threads (click, click, click) ...

To clarify, the moderating team's message to you explained that your prior post was hidden from view because it described a workflow using an "unauthorized application," but the message went on to say that it is fine to "use the Geocaching forums to discuss the official Geocaching apps and authorized Geocaching Live! partner applications." Therefore, it's fine to talk about solutions involving GSAK or Cachly, for example, because these authorized partners use the Geocaching API. That said, the OP asks about websites, not apps.

First, if there's no issue with the cache, then answering reviewer questions shouldn't be a problem or an issue. Rather it should be great if he can talk to a reviewer and confirm that the cache is good to go; that firms his stance and the cache status. Second, if his initial response to your OAR log is anger given what you said, that is not a nice CO and I wouldn't bat an eye if the reviewer decided to do something about the cache. This is another reason why having a strong community is so important! More local events, let cachers meet each other and get a sense of who each other are and what their ethics are. Even ideally build a good rapport with others around. hmph.

I've been all about challenges for years. We started the Challenge Talk podcast in 2020 which is great for challenge enthusiasts. Personally there are so many challenges in Ontario now that I'm not so much working focused on specific challenges any more, but passively working on any I don't qualify for yet As mentioned above, I have a doc that lists all the challenges I know of and I periodically update them all with current progress, and whether they're qualified (then log it as such with a note); and if I sign in first I mark it in the doc as found as I know once it's qualified I can just log it found. Going on trips is prime time to prioritize finding qualifying caches. But I also have them sorted by priority. Dates needing find specific qualifying caches go straight on my calendar so I know "today I've got to find 5 caches, 2 letterboxes, 1 Other, and a 3.5/4" for example. If I'm traveling then region and location becomes priority. Any rare caches in the vicinity of travel go on the stop-and-find list. Especially region oldests, jasmer caches, rare DTs, or even just properties that don't appear nearly as often near to home. Rarely ever on a trip do I just casually find caches. There are too many and the vast majority don't help towards any qualifications. Even so, before casual caching I'd be searching for high favourite points for the best chance at maximizing my travel's experiences. Challenges give that extra goal, a new layer on top of regular geocaching (like geocaching on top of the real world :P)

Hi Groundspeak, I'd like to request an enhancement for the statistics page: make the cella in the Matrix 81 and the "Finds for Each Day of the Year" interactive. Ehen clicking a cell the correponding Caches found at this day or OF this D/T combination should be displayed. To come to this nice result today is rather complicated. Thanks in advance for realizing!

So, your talk about privacy was misleading. You are affraid of strange motivations. Let's compare this airtag with a logbook. Logbook reveals your private data. Logbook is tracking you not the airtag. You should opt-out all of them because there are huge number of airtag owners with more strange motivations compared to the OP. For example, a business owner may be tracking you when you enter the shop and can count how many times you have visited - spooky - isn't it?

If forum participants want to talk about challenge caches, the General Geocaching Topics forum is the place for that. This is the Creating Adventures forum.