Jump to content

Crazedllama

+Premium Members
  • Posts

    62
  • Joined

  • Last visited

Everything posted by Crazedllama

  1. If I hadn't started geocaching I wouldn't have met many of my best friends. I'm from Utah, USA, but I started geocaching in Korea. Living in Seoul, I've met and made friends with geocachers around the world. Before geocaching I only went to a few tourist places in Seoul. After geocaching, I've been all over the country and discovered amazing things that most Korean people don't know are in their own country. Then I visited family in Utah and was amazed to discover things I didn't know about in my own hometown.
  2. I've used a measurement app on my phone in the past. Obviously that could only be done for small things though. For my earthcaches, when I ask for measurements for big things if the cacher gets anywhere in the ballpark of the right answer I let it slide. Those usually aren't the most important logging requirements on my caches.
  3. Any accurate map is actually illegal in China. If you're caught using one they may confiscate it and send you to a local police station. Geocaching follows the law, so they only provide to you the maps that are legally used.
  4. I didn't get this message but a few years ago I saw something not so family friendly in a profile photo and username. HQ locked the account deleted the photo and renamed the account within minutes of my email. The people at HQ work really hard to make sure everything is family friendly and fantastic. Ill always remember that prompt response.
  5. I think that I'd probably just let it be, if I had a suspicion like that on one of my Earthcaches. Geocachers helping each other out with answers to mystery caches and Earthcaches is probably fairly common. A suggestion if you really care about maintaining the log. I would require that a photograph be taken somewhere near the Earthcache. It's difficult to prove that someone plagiarized answers, but its much easier to prove photographic evidence.
  6. I apparently wasn't clear enough. Many geocachers solved this cache. Contacted 60 or more geocachers around the world, just to be told by the checker they had to physically be in Vancouver to get final coordinates. This is also a place that the owner themselves had likely never been to. Furthermore, you have to be connected using a local IP address without proxy, so if you are using a foreign phone or foreign data plan, coordinates are literally impossible to get without talking to a local. When I plan vacations to foreign countries I need to meticulously plan my vacation because I'm always with muggles. A big change of plans to go to a place I didn't expect because I could only get coordinates near the spot means that cache won't be found. After all the work getting to that point, it'd be really frustrating. I'm not advocating for sharing final coordinates to most mystery caches, but this one I don't see the problem because literally only a local can obtain final coordinates.
  7. I think that a few of the people posting above may not have actually worked through this puzzle. It is designed in such a way that even if you do work with people from around the world that the final coordinates cannot be obtained unless you are physically standing in Vancouver. Many of the geocachers who worked on that puzzle felt cheated when the checker told them to visit Vancouver for the real final coordinates even though they had helped get the answers for local cachers. The real kicker is... The CO of that cache likely has never been to Vancouver themselves. Personally, I would share coordinates with anyone who had helped work through this kind of puzzle with me. Other types of puzzles, probably not.
  8. Our reviewer in Korea is GeoAwareEU1 too. They are a great reviewer whoever they are! 한국에서도 GeoAwareEU1 어스캐시 리뷰어 돼요. 진짜 좋은 리뷰어에요!
  9. A few months ago I logged an ftf NA. The reviewers missed that the cache had been placed in a restricted military area and a day later the cache was archived.
  10. I thought it was strange that even though they're Ninja Turtles, there wasn't a single event in Asia... Then I looked at NYC where the Turtles are from and there wasn't even an event there. I guess most of the world just gets skipped this time. However, I am happy that I can enter the drawing to receive one this time. We always get left out of geocaching promotions here in Asia.
  11. Thank you for these recommendations. You were all very helpful. I'll wait a few days to see if the geocacher responds to my messages. Then delete the photos and log a note if they do nothing.
  12. I recently received a log for one of my Earthcaches. All the answers are correct according to the logging requirements. I also have a photo requirement for the cache because it was recently published in line with new guidelines. The geocacher also posted a photo in line with what I ask. However, the geocacher gave the answers to the other Earthcache questions in the titles of the photos. I asked them to rename or repost the photos, but I don't expect this geocacher to actually do this. I was going to just delete the photos, but then in the future, other geocachers may question why they must post a photo when this cacher doesn't have one. What would you do? Thanks for the advice.
  13. The FTF thing is really just an annoyance. The bigger issue is that this cacher wasn't using a puppet account, but actual people's accounts to hide their activity. Also, when they were caught and called out they archived hundreds of caches, that they shouldn't have been able to access to in the first place, which are now more difficult to find. It's also been near impossible to keep geocachers active after they see the #1 cacher acting this way and getting away with it. Just isn't as fun any more. Also, you're right Japan has similar customs, but somehow they've been able to avoid similar problems. They've also been able to grow their community of cachers, something that Korea has been unable to do.
  14. This seems nice, and I would definitely call out this cacher if I saw them somewhere, but I'm the odd one out in a country where the culture almost strictly forbids calling someone out in public. Shaming someone in public, even for something that everyone knows they did, can actually get you sued for slander. Reputation is everything in Korean culture, but publicly calling someone out for something wrong they did is considered even more shameful. I know, seems weird.... A good example of this is when we had a different cacher a few years back hiding caches upwards of 80 meters off coordinates and just supplying a photo spoiler. The Korean geocachers would log only positive things or quick logs like tftc, when the foreign cachers started complaining, the cacher archived 1000 caches countrywide to avoid the public shame. In reality, I think only Groundspeak can do something to stop this kind of behavior and I think previous suggestions from above like making adoption logs a new log type and locking them like a publish log would be locked will help. There would still be ways that this cacher could log their own caches ( ex. team/puppet accounts), but everyone would know it was him so I doubt he would continue.
  15. In the USA, I agree, I wouldn't care so much because it wouldn't affect the general geocaching population. That and more cachers are likely to call out the bad behavior. However, over the past several years we've seen the geocaching community shrink to around 15 geocachers Korea-wide because of these kinds of actions. Also it has become near impossible to recruit new geocachers and keep them in the game. They start playing and then quit soon afterwards when they notice the "#1 Korean Geocacher" puffing up their numbers so much. I think this is a case where Groundspeak has misunderstood Asian, especially Korean, culture where being #1 and the actions of the #1 person in a community really matter a lot. I think the reason this geocacher has done it in the way he has (by placing a cache, adopting it over to a previously legitimate account, deleting adoption logs, changing the name associated with the cache, then logging a find) is to #1 avoid scrutiny from the reviewers who knew about the previous players' death or inactivity. #2 Avoid scrutiny from the geocaching community by using a name they all recognize. #3 Avoid the shame of cheating and being found out by the community. Our local reviewers (who understand Korean culture quite well) when they found out what this cacher did permanently locked the adopt notes on all the caches he had adopted so as to expose the shame. Then Groundspeak locked the account as soon as they knew what was going on. Groundspeak's biggest mistake came when they allowed him to readopt all of the caches back to his original account. In the short time span they gave him, he archived all of the account's original caches (close to 500) and then adopted all of the other caches with locked adopt notes to another puppet account and archived them too (to hide his shame). So now, there isn't any proof on active caches that he had ever done it. In the end to avoid the shame he archived hundreds of caches across the country just to avoid being shamed. So maybe meaningless to you, but if Groundspeak actually wants to attract new geocachers in Asia who will pay for subscriptions, they're going to have to deal with this kind of behavior more aggressively. Otherwise, the community will continue to decline.
  16. You could do this with dropbox/amazon/any cloud service links. Keep the links in the notes on your cache then forward the link to a geocacher if you wanted. I've been sent dropbox links from COs before after a dnf and it worked well for me.
  17. I like this analogy. Makes sense to me. When I see that a cache has been adopted, I understand that the owner has made an effort to keep their cache alive rather than letting it die. With what was happening here in Korea keeping the adoption log would have been an easier way to see that the caches were actually under the same management. I like some of the ideas posted above that maybe an adoption log should be its own log type and I think maybe it should be like a maintenance log that wipes the CHS slate clean.
  18. We're glad you decided to come anyway. There are so many amazing places in Korea. We just wish the country had a better geocaching reputation.
  19. Would deleting a log even change anything with CHS? I guess that's a question for another forum. The appearance of issues is definitely why we had a problem in Korea in the first place. He thought by deleting the logs, no one would notice. That's like a cacher who doesn't dnf a cache for fear the cache will get archived or deter future finders.
  20. I could get on board with this. An adopted cache just almost seems like a new listing to me, so a formal transfer log seems necessary. Maybe that's why it seems strange to me an adoption log can be deleted. It's almost like it's being republished. Ugh... In this case I would've received thousands of emails in a single night just to look at the cache listings to find the logs had all been deleted. It would definitely do what you say, but at the sacrifice of my email inbox. Haha I actually only noticed the strange behavior from my pocket queries of unfound caches. They suddenly had new owners with no adopt logs.
  21. I stand corrected. You're right. I've never seen any cacher delete these logs and thought I remembered seeing warnings when editing the text before. Not sure why these logs would need to be deleted either. Anyone know why someone would want to delete a disable or maintenance log?
  22. You're right, reviewers and HQ can absolutely see deleted logs, but they can't be everywhere and don't tend to go looking for violations. It was us regular geocachers that caught on to the strange behavior in Korea, not the reviewers or HQ. Reviewers and HQ tend to rely on the local communities for input. (A reviewer told me this). And when those logs are delete-able it's difficult to spot potential problems. I don't see a problem with archive graveyards either. Not my style, but to each their own. Locking adoption logs automatically would be an easy way to expose potential abuse while it's happening. If a cacher bounces a cache between multiple accounts it would throw up red flags in the community that something strange is going on.
  23. He was using their passwords, or... That's what we assume he was doing. The response we got from HQ when he archived close to 500 of one of those cacher's original caches was that because they gave up their password, they lost control of their account. I'm not sure why he thought it was ok to use a deceased person's account though... Regardless, he didn't cover his tracks well enough and the accounts were locked. There are about 5 other puppet accounts he has though. I was afraid that the log was just note type and maybe nothing could be done. Couldn't a script be written to automatically lock a adoption log upon adoption? Right now it just seems like this cacher has caused a lot of unnecessary work for our reviewers and HQ.
  24. He was impersonating another already existing geocacher, and it was his second time doing so. Groundspeak did get involved, both times and locked those accounts. That's not really what I'm asking though. Essentially, why was he able to delete the adoption logs in the first place? Wouldn't it be easier for Groundspeak and the hard working reviewers to lock all adoption logs so they can't be deleted? It just seems like the cheating would've been more difficult to hide.
  25. The local reviewers and Groundspeak are aware of the issue and have restored and locked many of the logs, but they are volunteers and there are thousands of instances of this geocacher deleting logs. My broader question is why is it even possible to delete these logs. They seem just as, if not more than, important as other types of logs that cannot be deleted. It just seems like a great way to cut down on this type of cheating.
×
×
  • Create New...