mustakorppi

Or someone from Canada. But yeah, I didn't look at the regional wiki: https://wiki.Groundspeak.com/display/GEO/North+Korea

https://coord.info/GC2F0R6 I don't see a reason why someone couldn't create e.g. a Wherigo that starts in North Korea and ends up wherever is convenient for them.

There's a thread in the Finnish section of these forums from 2008 complaining about new users only logging with a smiley face. But if you want to continue discussing new user onboarding in ways completely unrelated to fav points, perhaps another thread?

Yeah, that's what I said. The app has it's problems, but the way it avoids inundating new users with inconsequential information is one of the things it kind of does right.

I'm referring to the cache page in-app. Not the cache description, not the website. Look just below the Navigate and Log buttons.

The heart icon and the word ”favourites” are shown on the cache page. The icon changes if you’ve marked the cache as favourite. So yeah it’s not explained but I guess most people can figure out the rough idea, which IMHO is plenty for such a non-essential part of the game.

I have the old CD-ROM version of Oxford English Dictionary 2nd Edition, from back when dictionaries were still something one could buy instead of rent access to... The OED does not know the word 'hectagonal'. The only word starting 'hecta' it knows is 'hectastyle', which it lists as an erroneous spelling of 'hexastyle', meaning 'Having six columns; applied to a portico or to the façade of a temple' The word 'hect-' or 'hecto-' is listed as meaning hundred, and the OED does list a number of words using this prefix. Presumably one could also form 'hectagon' and then 'hectagonal'; there just isn't evidence of a native speaker (whose writings the OED editors have perused) having done so. And the meaning would obviously be very different from 'heptagonal'. (Getting this ancient 16-bit application working on a 64-bit Windows 10 was a bit of a headache. It mostly works by running WINE in Linux running in Hyper-V -- essentially Windows emulating Linux emulating Windows- - but the fonts that would correctly render the Greek word for hundred used in the definition of hect-, hecto- are unfortunately missing...)

Sometimes get this on my ipad, possibly related to trying to tap on a cache on the map just after it has been loaded.

Indeed, or get rid of everything except trads. I guess it's up to what's the plan for geocaching. Is the idea to improve it finding a clearer focus? To expand and explore new things? Try to perfect what it currently is? Just let it be until it's no longer profitable to keep the servers running?

Could you please re-read what was proposed. CO is free to change the cache page, it just wouldn’t retroactively change what previous finders found. A cache you’ve found can change before the challenge cache it’d qualify you for even exists. I mean, I don’t particularly care what the mechanism is. But how many characters would it even take to describe all challenge-relevant data if you tried to be efficient about it and didn’t care about human readability? 30-40? I don’t think it’s much of an issue either way. This is a whole another discussion, but there are quite a few things I feel aren’t worth it that HQ still spends time working on. Some things I consider a net negative, even. This? Yeah, sure it’d require some work. But at least it’s work on actual geocaching, and I can’t imagine what harm there would be in found stats more accurately reflecting what you’ve found.

Well yeah, why not do exactly this for everything that the rules allow to be challenge criteria? How does me keeping track of something like this help when a CO runs a challenge checker and sees I don't fulfill a challenge because a cache changed after I logged a find?

It’s a coin toss whether the maps on the website even load properly so…

This has changed sometime in the last few days, apparently with no announcement. A fieldset element is expected to render with a visible border by default. Now it gets a border-style: none; from somewhere. This messes up a number of existing cache descriptions' layouts. Any user-applied borders and stylings get stripped away on save.

Does that thread still exist somewhere? Can anyone find it? I have vague memories of even posting in it, but I can't find it anymore...

This was in reference to Goldenwattle's idea that a magnetic cache high up a lamp post cannot be T1.5. If you don't bring the appropriate tool to retrieve the cache from the ground, that's not a problem with the rating. If the CO is intentionally jerking people around (e.g. by omitting the special tool required attribute), then I personally have no issue with returning the favor. But messing with correctly rated caches just because you choose to interpret the ratings differently isn't right. Having to cross sand, boulders and cliffs is an entirely different matter.

If in doubt you could always ask the CO. Or post a maintenance log. This particular case, whether a cache that's high up but can be retrieved and returned with a tool without moving from the ground should have a high T rating, can legitimately be interpreted both ways. Your interpretation doesn't match the HQs, but that's beside the point as far as I care. The people who take it upon themselves to enforce HQs interpretation by attaching other people's high T caches up in trees so they can't be fished down are equally in the wrong.

"Return the logbook and cache to their original location"

The one time I've hunted a cache like this, I got to the first waypoint the same time as the "birthday girl" and we did the rest of the cache together, joined by the cache creators near the end. There were two groups of hunters ahead of us the whole time and at no point did anyone even hint that etiquette was being breached (except with regards to one group of hunters apparently taking a shortcut through private property). But essentially, published caches are fair game to all and FTF hunting is a race. It can be a friendly race full of cooperation, but it's still a race and you can't show up to a race saying only one person is allowed to compete. If you want a private caching experience, don't publish the cache. I wasn't around in the early days but I know it was reasonably common for hiders in my area to publish the cache details on IRC or their personal homepage etc. while waiting for approval on gc.com. Today it would be a faux pas to claim an FTF on cache before it's listed, but I assume the "honoring" here is supposed to be the cache itself, not awarding "points" in a sidegame. Your local practices may vary of course.

Not really interested in entering remoteness contests with Australia I have replaced someone else's broken down container (and logged a find) at a ski resort that doesn't seem to support a native geocacher population, but sees a lot of people coming to find caches. Apparently the container I placed has since broken and been replaced by someone else. The way I see it, either the visiting community maintains the existing caches, or there's no caching in that area (apart from containerless formats I guess).

Because that 1% is also mostly smartphone cachers. Who cares, in the context of this particular topic, what people who only find a few trads every now and then use.

What an utterly ridiculous claim.

I'm sorry to second guess you, but is this really correct for multi-caches? Mystery physical stages sure, but I would have assumed it's too much for a multi. Unless maybe you can require that the QR code gives the directions to the next waypoint directly, instead of, say, pointing to a website with a puzzle...

Open the cache in app and swipe down to make it fetch updated data.

Yeah that's the one. I think that it's more than a bit silly that calculating an area inside caches is not allowed for a challenge, but calculating distance between caches is.

The "What can we help you with?" selection doesn't have an option for reporting caches that don't comply with guidelines.