The A-Team

Ah, I see now that they fixed the wording on that page. Originally the wording was ambiguous, but now it clearly describes the page: Thank you to the person at HQ that changed that.

The graph on my stats shows bars right up to February 2020. It is wider than the viewable area, though, so there's currently a scrollbar that I have to use to see the last few months. Do you have that? You might just have to scroll over.

Just to be clear, when I said "acceptable", I meant acceptable as far as the Terms of Use for this forum. What might be acceptable culturally in your region may not be acceptable here. I've been known to call people idiots in real-life, but I wouldn't do so here.

I agree. On its own as just a raw number, it really isn't all that meaningful. Let's say I look at someone's profile and they have 50 FPs. Is that good? Was that on one cache or a hundred? Were they over the course of the last six months, or the last 10 years? How does that number compare to other hiders in that area? With the increasing levels of abuse in the trackable side-game, I support the removal of the trackable count from the public profile. I'm not sure there's much benefit to be gained from the total FP number, though, at least in the public profile. Maybe it would be more useful to have it in the private stats for the member, since they're the ones with sufficient context for the number to be more meaningful.

In order to help clarify what's allowed and what isn't, here are a couple of examples: 1. "I understand why you think that, but I disagree and think that..." 2. "You're an idiot" 1 is acceptable. 2 is not.

I recently encountered this error in version 1.2.6 of the iPhone app. On February 1st, I made my way through an Adventure with no apparent issues, but then got this error when I tried to submit my completion log. I hit "Try again", but I got the same error again and the app then backed out to the main screen for the Adventure. It said I had completed the Adventure, but I didn't show in the activity. The next day, I realized that I was one find short of what I'd expect, and the app was now showing that I had only completed 4 of the 5 labs. It didn't register that I had found the 2nd lab, even though this was a sequential Adventure and completing the 2nd one was mandatory to get to the last three. I tried the offered option to "Resume", but completing the 2nd lab and entering the completion log just gave me the same "Unable to post log" error and nothing changed. I thought that maybe if I deleted the four finds that registered, I could start over and hopefully it would work this time. I deleted those finds, but the app still says that I've completed 4 of 5 and I'm now stuck in a state where I can't log any of the labs in this Adventure. It turns out that I'm not alone. In our local Facebook group, there are 5 other cachers that encountered similar issues on multiple Adventures in our area. This has happened both on iPhones and Androids. I've sent in a support ticket to HQ and am now waiting to hear back. Has anyone else encountered this? At least in my area, this problem seems to be fairly widespread.

The number of cache hiders and finders in the case of Netherlands Antilles is relatively low, so the outcry of not making the change would have been minimal. In the case of a constituent country splitting from the United Kingdom, there would be a lot more people wanting the change and I expect HQ would plan to make the necessary changes right at the time that the split officially took effect.

The new Edge (known informally as Chredge or Edgium) is based on the same underpinnings as Chrome. If something works in Chrome, it should work in the new Edge too. It isn't that the site has been fixed to work with Edge, but rather that Edge has changed such that it isn't affected by the issues. The new Edge is optional, though, so there's a good chance that there will be lots of people still using the older Edge for a while, and it would be ideal if the various issues could be fixed so that the site works in old Edge/IE11.

I'm not sure what you mean. Do you want to see what the souvenir will look like? They don't usually do that ahead of time.

Agreed. There are so many variables in play that there can't be a fixed "standard", so it's then hard to say if anything one does is "above and beyond". What one person may consider "above and beyond" may be what everyone has to do regularly in another region. Personally, my maintenance strategy is built on a foundation of choosing an appropriate container and an appropriate hiding spot. Once you do that, the need for regular maintenance is greatly reduced. I have some caches that may go 5+ years without me checking on them, yet they're still in fine condition. Beyond that, maintenance is largely on an as-needed basis based on what I see in the logs. If I happen to be passing by one, I'll quickly check it to see if there are any issues.

That is odd. I was expecting that the description might have some unclosed HTML tags or something, but the description is just a few lines of plain text, and nothing has been entered for a hint. Database gremlins I guess.

I accepted the default cookie settings and don't run any script-blocking add-ons, and I don't have any issues using Firefox. That may not be the problem. I seem to remember some people initially saying that they only allowed the "required" cookies and then found that some features weren't working. Could that be the case here?

There's one for Puerto Rico, though it's only a country in the context of this site, not in the broader non-Geocaching.com sense. Cuba is the only other one that has a souvenir so far.

This is a known issue. It was actually a previous release from about a month ago that broke some functionality when using the Internet Explorer or Edge browsers. They're working on it now, but in the meantime you'll need to use a different browser to perform these actions. Chrome and Firefox have been confirmed to work for things like editing or deleting logs.

The cache you're looking at hasn't been published. If you look at the listing of a published cache, that feature should still be available. They haven't taken it away.

nykkole posted this last week: If you're having any issues, maybe contact HQ directly to tell them what aspect isn't working so they can see if they can make it work with the proxy server.

Things seem to be working for me now. I'm able to sign back in and access various pages. Edit: Cross-posted with Frau Potter. Thanks to the engineers for jumping on this on the weekend!

Yep, I'm getting lots of 500 errors and can't log in. There are also issues with the API, with only a few calls completing successfully and most failing.

Yep, there's no required minimum distance between stages. I've found stages with no horizontal distance between them, as well as a couple with a distance of about 1 inch. One of the latter was hidden by a Lackey.

This would be dynamic. Each time you go to your bookmark, it performs the search and shows you the current results.

Well, you don't have any points, so there's none to lose. As for your find count, yes, that would be reduced to 0 in your scenario.

I understand that, and I apologize for the wording of my last post where it implies that you're part of HQ. Your original statement seemed definitive (reviewers are often privy to more information than we are), so I thought it reflected an official HQ position. I'll stop discussing the matter of IE11 support here. You may see it as nitpicking, but everything I post is ultimately intended to help in some way. Whether that's correcting a faulty statement or identifying a flaw, the goal is to ensure information is being discussed accurately and issues get resolved. I whole-heartedly encourage other volunteers to post more often. Engaging with the community is the best way to build a healthy relationship. It won't always be sunshine and rainbows, but that's the way most relationships are.

I think it's more about whether something is happening automatically or not. In the case of an img, the user doesn't choose to view the image or receive any related cookies; it just happens without their input. With a link, the user has to consciously click on the link. I guess choosing to click a link is implicitly accepting any possible consequences.

In Microsoft's own words, they still support IE11 until the end of Windows 10. Sure, they aren't making any feature changes, but if they say it's still supported, then it's still supported. It should also be noted that, as barefootjeff posted above, the Geocaching.com documentation still lists IE11 as being a recommended browser. If they don't want to officially support a browser anymore that they used to support, then this needs to be communicated to the members in some fashion. Currently, other than Keystone's post and a few Lackey posts suggesting that you should try a different browser, every indication from HQ points toward there being no change with respect to IE11 support.

That's understandable for design decisions. As you said, you can never please everyone. However, if something is broken, the expectations are different. Really, there's only one expectation: the broken thing gets fixed. This is a Boolean decision: it gets fixed (to some degree), or it doesn't get fixed. If TPTB are looking into the issue, then it would be great if they could tell us that. I know they don't like saying things like that and making a commitment that they might not be able to meet, but the expectation from the users is already there anyway, so it won't hurt anything to actually tell us that it's being worked on. Being transparent and communicative is an excellent way to build a good relationship with your users. On the other hand, if they've decided that the proxy is working well enough for their purposes and they won't be looking into the cases where it isn't, then we definitely need to know so affected owners can make the necessary changes to their listings or archive them. As always, there's the "do nothing" option that seems popular, but the consequences of taking this option need to be taken into account (loss of trust from the users, confusion leading to a higher number of support requests, users making and spreading incorrect assumptions, etc.).