Search the Community

Same with a lot of high Terrain rated caches... Well to be fair, there's not really a universal objective measure. One person might believe that a single fizzy is a true 5 difficulty for them, or in their region. Go there from a place plastered with all DTs and that 5.0 Fizzy challenge is clearly overrated. A newer cacher putting out a challenge cache might not consider such accomplishment as easy and 'overrate' it relative to loads of others in the local community. Ultimately the rating is up to the CO, and unless we know the CO and the region, it's hard to say whether a cache is 'objectively' (or intentionally) over or under rated... For both D and T, I think the jump from 4.5 to 5 could be either an underrating or overrating. For me, a 4.5D puzzle could be very hard, then next to it a 5.0 programming puzzle - that's a step down for difficulty for me, but for someone else without that specialty knowledge, it would be an easy 5.0+ difficulty (unless of course they just ask someone for the solution, which typically happens around here). So I think the 5.0 D or T is a rating all its own, and is hard to classify it universally in relation to the 4.5 rating, because most of the time, that 'specialty' tick (equipment or knowledge) is either going to itself be easy or hard depending on who you talk to.

I wish I could talk to someone in person, but I've been told to contact the land manager in another state. This will be an urban cache.

That's fairly rare. How rare depends, I suppose, on which part of the world. These are what keep the game interesting! I've found a handful that have been waiting longer than that for their first find (memorable, all of 'em), and own one that still hasn't seen a cacher reach GZ for 9+ years now. I'm sure some people have their eyes on it. Oh so Blue in Belize was 8 years before the first find, and there was quite the forum discussion leading up to it. I almost went because I was nearby. Coulda shoulda woulda... (All talk, no walk.)

Hmmmm, seems like I had a small breakthrough here (after several breakdowns): I created this Input: Then I made this flow to handle the "On get input": Then I put a "Talk to girl" command on the "Girl" character and eneabled/handled it: Now, if I click "Yes" the girl is moved to my inventory, and if I click "No" the message is shown with an "ok" button. If I click the "ok" button I am returned to the main screen and can try to accept helping her instead. There are so many "Unhandled" places to click that it's a bit of a jungle at first. Is this a good way to handle this, or are there better options available. Don't get med wrong, I'm pretty happy to get this far. I also wonder how to prevent the input "Talk to girl" from running when she has been moved to my inventory and I click on her?

I'm curious that in the Blog post they talk about tackling a T5 climb or solving a tricky field puzzle and say they're celebrating the diversity of embracing your own version of adventure: Adventure takes on a unique form for each of us, whether it’s the thrill of climbing to reach a T5, solving a tricky field puzzle, or exploring a new area of your neighborhood with Adventure Lab®. What’s important is that you’re out there, embracing your version of adventure. This year, we’re celebrating this diversity with a special souvenir! But you can only get the souvenir by doing a stage (not the whole Adventure, just one stage) of an AL. I guess for me the "adventure" will be the long drive through Sydney's traffic snarls to get to the nearest available AL stage, but that's not an "adventure" I'm all that keen to embrace..

For anyone interested there have been a couple podcasts this week about Wherigo. The first one is put out by Groundspeak and gives a little information about the development of Wherigo. Although the part about Wherigo is pretty short, it still gives some interesting history about the team who created Wherigo. https://www.geocaching.com/blog/podcast/episode-31-jen-smith/ The second video is a tutorial/template for creating a simple Wherigo with URWIGO. Enjoy!

Sorry, I have no idea what you want to say here. Maybe my english is not sufficient. Lets try again. By "Picking up" a TB I meant someone "retrieves it from the cache" so that does not include a visit log but only a "Retrieve log" What I meant with hoping for a "surprising log" is that scenario that the TB somehow gets lost without any trace so you gave up any hope but suddenly the TB shows up again and was correctly logged (grabbed+placed). Probably in that case even I would be happy about a meaningful(!) discovery log I certainly don't talk about "your" or "cerberus1s" logs which apparently (at least in my experience) are an exeption to the rule. And yes visit logs are usually by far more annoying than discovery logs because of their volume.

I want to start by saying I worked with many reviewers (probably something like 12) and I generally find them amazing people doing great work. If anyone starts digging after reading this, I want to also state explicitly that it is not about my usual local reviewer, who I find to be extremely professional and helpful. I am trying to publish an earthcache and I am finding the way the particular reviewer who's looking at the cache approaches the process unacceptable. The process has been going for way over a month already and hasn't really moved forward during that period. It's generally been going something like this: - the guy asks me a question - I answer somewhat extensively - the guy takes over a week to answer and asks me another question, not at all related to what he asked before. If he does expand on his previous question, he seems to not have read my answer at all, at best having skimmed it In his most recent response, today, he asked me to change the cache entirely, dropping 4/5 questions. He didn't provide any good reasons, his reasons were twofold: 1. "This is not interesting to anyone" - I find that to be purely offensive and not really professional in any way. It is interesting, at the very least, to me, which is why I am trying to publish a cache about it. 2. "This is not geology" - In one case, he used that argument when he was talking about a question which says, literally. "How does this [high concentration of heavy metals] affect the geology of the soil?". In the other case, he said this because the cache talks about a river which was regulated by humans - but the fact that the river was regulated has nothing to do with the subject of the cache, I only mention it once, just so that people are aware, and I only talk about actual geological aspects of the river, not it being regulated. Needless to say, I do not ask any questions about the regulation or human interference in the river at all. I believe the guy to be completely wrong. But even if he were right about the crux of the matter, I find the way he doesn't address what I said to him and changes his mind about what the problem is constantly, to be unbearable. My question to you is, if he continues to be so difficult, is there anything I can do about it? Can I ask for the cache to be handled by a different reviewer? Can I ask Groundspeak to double-check our messages and ask him to be more reasonable? Are there any other steps, formal or informal, that I can take? I am asking this here, not in the earthcache forum, as I believe the actual question may be relevant to people outside of earthcaching, but facing problems with reviewers more generally. Thanks in advance for any advice!

"There's probably some "clever" bit of code in either the app or the phone's GPS service that thinks it can save a bit of battery life by not taking readings when it thinks you're stationary. I've worked with - and on- that clever code. These days it's a feature in the correlators called "static navigation" that can be enabled, disabled, or ignored. A GPS never knows where it is. I knows within N% confidence that it' somewhere inside a circle of R meters. As the ionosphere changes and the constellation moves, that circle and its assumed position in the point cloud will change. If a GPS in your car reported your position as moving back 2m NNE this second, 3NW this second, 5m SE this second, and so on while you were waiting at a stoplight, you would through it through the window, especially if that drift took you into an adjacent land and the girl in the box shouted out "rerouting1". As some point, MOST users want 'stopped' to mean stopped. If you're a geocacher looking for a tube stuck in the ground (ew!) you may actually want that, but most civilians don't. That mode is called Constant Navigation. I didn't know what it was called when I wrote this page 18 years ago (I wasn't even sure it was still public, actually) but I graphed three of the most popular GPS receivers in .. 2006(!) I sat a GPS 60Cs (the one with the stupid chip that would lose lock in tall grass) the 60CSx and the Magellan Explorist 600 and collected the location that it reported to the computer over the course of many hours. The 60CS basically didn't know where it was. The 60CSx of that era roamed all over, traveling over a mile while..sitting at my desk while the Magellan - which was famous at the time for doing a bit of aggressive position averaging - moved less than 1/5th of that, with about half of that in one short burst. Those last two actually used the same GPS chip, the SirfStar III, and I now believe that one used static navigation setting and one used constant navigation. https://www.mtgc.org//robertlipe/showdown/index.html I think Atlas' answer is probably the "right" one, IF there is an actual measurable difference. In the old days, people were more meticulous and more "gadgety" in respectful use of their equipment. Now, it's taken for granted and it's much more likely to talk up to a rock, drop a box behind it, snap 'mark' and walk away instead of taking 30 minutes of averaged locations as was common when coordinates came in roman numerals. As for the tease at the end that was fashionable in that era, I lost interest in caring about such things and was still able to go outside and play instead...

There is a limit to the distance you can update the coordinates to. Also hopefully it does not infringe on a proximity to another cache. Talk to your reviewer they can definately help and should be able to quickly tell you if there is a problem.

I haven't taken the survey yet. Any thoughts from those of you who have? https://www.geocaching.com/blog/2018/12/lets-talk-some-more-about-geocache-quality/

I use both my Android and an Etrex 22x. I've been checking out different apps on my phone. I've been bouncing between Geooh Go and the regular app. Geooh Go has some cool features the regular app does not have. I like having access to Wherigo and Project-gc directly in the app. I don't like the GPS function so I use my Etrex 22x for gps. I use my phone to log caches in real time with the talk to text feature to create my logs.

I'll just say that it's not too hard to find once you start looking. Talk about hidden in plain sight!

Yeah... I went to find a couple caches for a promotion. Most had maintenance issues, but one was only the top of a bison tube. People were finding that "top" and claiming it a find for over a year. A jerk like me (by talk at events) comes in and NM it. The only NM on that cache... The "CO" got in a huff and archived all caches in the park. I picked up the bison top and a couple others two weeks later, but there's a bunch still there. People were happy to find a top and claim it a find...

Talk to text?

Skimming topics, i decided to dip into the other remaining source of GPS expertise, the GSAK forum. (Duly noting that OP is on a Mac and this does them no/little good.) https://gsak.net/board/index.php?showtopic=36383&view=findpost&p=279765 concludes that there is MTP voodoo within GSAK (!?!?) Perhaps, this being a Microsoft creation as part of Windows Media, plinking around media files is easier there and GSAK somehow hooks to some kind of OS interface to do this. (We've also had people declare the end of Garmin MTP about every six months since the original Nuvi 350, so I don't know if the 67 is really really the end or not...) Still, when I see authoritative-sounding MTP Library things on the web saying things like: It seems quite likely that if Clyde came to me before May, 2008, I'd have told him to take off as it's MS-only and after May, 2008, I'd have told him to take off as sounds like the standard compliance is poor and reading things like https://github.com/libmtp/libmtp (search for 'kext') encouraging people to disable their USB mass storage devices, which requires unlocking several security checks, it just sounds like a bad idea even on MacOS. (I can be a jerk like that...) In that same doc, we have both: "Windows Media Player apparently never close the session to an MTP device." ... "The "Unix way" of running small programs that open the device, do something, then close the device, isn't really working with such devices and you cannot expect to have command line tools like the mtp examples work with them." You may be able to think of a program that very much embraces The Unix Way. It seems likely that you'd be deeply annoyed at GPSBabel running forever or requiring you to reboot between times of talking to your GPS. That's just incredibly dumb, but that's 2000's era Microsoft for you. So even now, if they were to ask, the words "take off" may not appear literally in my response, but without someone else paying for the engineering to bring a quality MTP implementation into GPSBabel along with a device testing budget, I don't see it happening. Heck, Maybe Garmin had to develop one for Basecamp that's usable open source (hahahahaha). Maybe iCaching is interested in developing some kind of code to talk to these things, but I don't particularly see this landing on my desk as an accepted action item without some divine intervention. (That happened on the 60 Cx...) Since I hadn't finished reading the entire internet before posting that (workin' on it!) it possible that https://openmtp.ganeshrvel.com/ may be better, worse, or at least broken in a _different_ way. It doesn't look particularly Mac-like for a Mac app, but I have no vote. Working + Homely > Attractive + Dysfunctional (This is also solid dating advice...)

Ok, let me ask you a question: Why does a magazine cover depicting a shot black kid (I suppose this is the cover in question) need to be on a geocache page? What does it add to the cache and the caching experience of the family trying to find it? Also, you talk about deflecting, but you don't say what the communication with the reviewer about placing a cache on a postal structure looked like.

I'm closing this thread because this is the forum for discussing Geocaching.com's smartphone apps - not for discussing handheld GPS units. There is a separate forum section to talk about GPS and Technology. There's a pinned thread at the top of that forum section, and the most recent post in that forum is in a thread asking the same question.

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)

Based on the other caches you found I could see that there are several events within say 20km of that find location coming up. Why not join and event, talk to people and learn more about placing your first cache there? The community is generally very friendly and helpful.

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.

Spam: Again, opt-in. Harvesting of usernames may be possible if replies are received, but that's also attainable from the gc website itself. Usernames couldn't be harvested from some central list since that wouldn't exist publicly. I'm sure throttling could also be implemented so bots don't spam every combination of letters to find valid/active forwarding emails. Incoming email: I'm not 100% on the technicalities of email distribution, but there's no email transfer to the gc servers if forwarding - the email process would have the servers exchange info and the forwarding server would simply be indicating the redirect destination. It wouldn't be millions of emails being transferred, just pings to tell the sending server where to send the email and how. Not much more intense I'd expect than the already inundated servers being hammered by bots and hack attempts. A ping is negligible; an email forward would be a bit more than a ping, to my knowledge. If that's wrong, then at worst the server receives the email and bounces the content to the forwarding destination server; nothing stored, just proxied over, and that's the last that's heard between them (a bounced destination, eg, would be sent back to the sender's server, not via gc's server). Managing addresses: This would, I think, be the biggest resource. However it wouldn't start out at a list of millions of forwards, and likely there wouldn't even be millions. If it's opt-in, then it would at most provide for active premium members who want to use it. Harvesting: Again, there'd be no way to attain a private email address from this opt-in feature let alone a list. Even after sending an email to a known active user's forward address, the user's private email would only be exposed if they replied directly to the email after receiving it in their own personal external email inbox. Only the sender's email would be exposed, on sending an email to the user - which, is, well, how email works. Email forwarding is a pretty standard fair feature of email providers. Of course GC isn't an email provider, and the system to be able to administer an email forwarding list on their existing email server would need to be built, but it wouldn't be building a complex email management solution on top of what already exists; just a tool to manage the forwarding function, and mitigate/throttle request overloads. All that said, I don't really see this feature being implemented, but it's fun to talk about. Someone might have a good idea for how to make it work in some optimal way.

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?

My map fails to load new tiles when I'm out of the data reception area. Such as downtown Peachtree City, or pretty much everywhere. Straight Talk Wireless is the worst! Yes, I know there are other phone companies. But I try to resist driving while watching for cache icons. Sure, a passenger might try it. But just seeing an icon on the map doesn't mean it's a viable cache. It may have been soaking wet and broken for years. If it's a park-n-grab, it likely is that bad. And it sure doesn't mean it's not out of your way. I've tried similar seat-of-the-pants caching where the icon is apparently right here, yet the approach is via the other side of town. Not to talk you out of trying it, though.

Thanks for the report. I can repro this issue. I'll talk to the team!