Jump to content

Crow-T-Robot

+Premium Members
  • Posts

    1317
  • Joined

  • Last visited

Everything posted by Crow-T-Robot

  1. There is nothing to review. Between the time that your cache might fall under the microscope of a reviewer and it being archived by a reviewer, you are given plenty of opportunity to either maintain the cache or submit a log explaining your plan to maintain it within a reasonable time frame. If you ignore that and the cache gets archived, that's your fault, not the "whim of a reviewer". Saying that the cache is in a remote area is not an excuse for the cache to not be archived. If you placed it, you agreed to maintain it. As long as there is communication from the CO, Groundspeak gives quite a bit of slack when it comes to caches that are disabled before they get archived but almost all of the caches that get archived by reviewers happen because the CO doesn't respond at all.
  2. I think a good compromise (if permission is granted) would be to go and buy your own brick, one that is a different color than the wall, create your cache and place it in the wall if there is an opening. That way you're not damaging any existing property and when people come to look for it, the odd colored brick will stand out to them. I think that would make for a fun urban cache and as long as you have permission to place the cache, shouldn't ruffle any feathers.
  3. If this isn't your wall, then you can't presume that "no one seems to care". Maybe no one would care that a geocache was hidden there but without seeking permission, you won't know that for sure. A bigger issue might be that when someone comes along to find the cache, they would have to remove the brick(s) to find the container. If the wall owner or maintenance person sees someone pulling bricks out of a wall that is already starting to fall down, do you think they would make the connection with geocaching? They would think that person is vandalizing the wall. You'd be putting finders in a bad spot and geocaching in a bad light.
  4. I know that large power trails are often pointed at as an example of why there should be a placement limitation and that there are a multitude of hiders that would otherwise be able to place a cache if not for all these spots being taken by one hider, but that has always seemed like a dubious claim to me. Even in the most cache dense area's of the world (Seattle, Portland, Prague, etc) new geocaches are published daily/weekly. There ARE places to hide a cache no matter where you live. It may not be in the park down the street from you but finding a good location is all part of the process/challenge of being an owner. Saying that owners that hide a large number of caches is keeping other potential hiders from placing their own caches also ignores the bigger problem, which is that so many of these caches within a power trail or series should have been archived long ago. There are exceptions, but most big trail caches tend to be hundreds (or thousands) of crappy micro containers that simply will not survive in the wild for very long but instead of being archived when they go missing/break, someone will always come along and throw down another crappy container to keep it alive. This keeps sooo many caches alive in perpetuity (not just in trails or series but overall, everywhere) that otherwise would've rightfully been archived. If you live in a cache dense area and want more places to hide more caches, I'd start with changing the mentality that geocaches, particularly power trail hides or series, somehow need to live forever. They should be like any other geocache: if they go missing (or become a hopeless mess), log a Needs Archive and wait for the spot to open up again.
  5. I am able to log in as of right now.
  6. It's your opinion that this account is a bot. Groundspeak doesn't share that opinion. The logs you've posted in this thread points to mangled english translations and/or someone that has odd logging practices but none of what you've posted is proof that it's a bot account. I think you're falling into the confirmation bias trap.
  7. I've used it and really like it. The pocket queries and lists download very quickly. I used it for one Wherigo and had no issues there. Probably my biggest complaint is that there isn't a way to access the compass once you go into the listing. If you click on the navigation option once in the listing, it will assume you're driving and open Google Maps. This can be changed in the setting to use a different navigation app but I didn't see an option to have it default to the compass. To use the compass, you click on the icon on the map and then the compass symbol on the same screen. It's not really that bad except when the first time you use the app and you're looking for the compass option in the listing and think you're going crazy not seeing it. Overall, I think it's a great app but I keep using the official app just because the official app has a better draft feature.
  8. I would still consider posting an NA. There are going to be other cachers showing up after you and if the nearby property owner is already irate at one person, they are not going to be less irate with the next half-dozen. It may not be on that persons property but they've shown that they're willing to chase people away. With enough irritation, things may escalate and this is just a game.
  9. I usually a casual enough user that most changes don't affect me enough to bother me, but this one...yikes. It does seem like at times, Groundspeak will send out a survey to 10,000 users and 5,000 of them will scream for X change, 4,000 want X, the other 1,000 don't respond and GS will implement something they assume the 1,000 non-responders must've wanted. Groundspeaks logic baffles me sometimes.
  10. Wouldn't it be better for the game to reach out and teach them how to use the tools correctly than to take the tools away from them?
  11. I had a multicache set up where WP1 would give you the phone # for a Google Voice account I set up. I used a free text-to-speech website to read back a voicemail greeting I wrote and in the greeting were the coordinates for the cache. I really liked the concept, but there were flaws that I couldn't quite resolve. Since I wanted to keep everything "free" on my end, the Google Voice account only allowed about 60 seconds for your voicemail greeting. I really like using humor when I can, so I wanted something more elaborate than a 60 second message but wasn't willing to pay out money to make that happen, so that was one limit. The other issue was that I Googled around for a good solution on how to get the text-to-speech audio recorded/transferred into my Google Voice greeting and there just didn't seem to be any good way. Maybe an inline microphone would've worked but I didn't have that on my computer, so I just ended up doing it the analog way...you know, by playing the file and recording it with my phone and then uploading it to Google Voice. The sound quality of the recording was...not great. It came out kind of garbled but it still worked well enough to glean the coordinates. I am still looking for good free/cheap solutions to this, as I'd love to create another cache like this.
  12. Ah, I see. I was looking at the Hides link in my dashboard and it doesn't show up there.
  13. It won't show in your profile as an owned cache. As far as I know, the only place that it shows you being the owner is in the Adventure Lab app or the lab creation page.
  14. I think the number of cachers who are logging fake finds from their couch is pretty small and those that do usually flame out quickly enough. I mean, how interesting can it be to mindlessly log caches just to see your find count tick up by 1 (or 10 or 100 or 1000)? I'm sure after a few hours, the reality hits them that they've been sitting here gaming the system for what? They get bored and do something else. Trying to patch that "bug" is pointless. There is always a backdoor method to fake log something but I don't think it's so systemic that geocaching needs to throw up roadblocks that will only penalize the honest cachers. Like I said, the ones that "find" caches without leaving the house might have their fun for a few hours, but it just doesn't hold their attention for long.
  15. You are correct in that the aim to review caches is within seven days of being submitted, but that doesn't mean they'll be published within that time frame. Seven days is just the goal to have a reviewer take a look at the listing. If there is an issue with the listing or the listing warrants more scrutiny, those caches usually take longer to be published. A more complicated listing will get put off to the side so the reviewer can publish the submissions that are easy to push through (to help clear out the queue) and then circle back to your listing and give it more attention. Also, many people were able to come out from under stay at home orders in June, so your reviewer may be facing an onslaught of new submissions to work through.
  16. Doing a little more investigating, it may not be a map bug more than an "Ignore List" bug. I just randomly looked at a map around Seattle and those Multi/LBX/EC, etc. icons all display fine, up to the closest zoom level. When I click on any of the icons that disappear in Wisconsin, those listings show as being on my ignore list. I just looked at my ignore list and there are a TON of caches on there that I never added to my ignore list. But that raises the question of why a cache on an ignore list would display at ANY zoom level on the map?
  17. I've noticed that when I'm looking at the map(using the "Search Geocaches" option vs "Browse Geocaches" option), if I zoom in to the 1 mile (2 km) level (or closer), the multicache, letterbox hybrid, virtual and earthcache icons disappear. The other cache type icons are still visible. Zooming back out to the two mile (and further distance) and the icons reappear. I'm using whatever is the latest version of Chrome at home and at work and I've noticed the same issue on both computers. I just logged in using the Edge browser and I'm getting the same issue. I don't have Firefox installed at work, so I don't know if it happens with that browser.
  18. I love viewing satellites. I've seen Starlink 3 pass over a few times now and it's cool but haven't been lucky enough to have clear skies when 4 & 5 were going to be visible. You can install the Starlink app on your phone to view dates and times when any of the Starlink satellites are estimated to be visible at your location.
  19. I guess I'm still failing to see how deleting the find will rectify any of the damages done in these scenarios. It doesn't and deleting the find is just a punitive measure. A person can be a jerk and still find geocaches. If you have evidence that someone broke the law when finding a cache, send it to Groundspeak and let them sort it out. You might not think they'll do anything, but there have been plenty of cache owners who learned otherwise when they tried to be the morality police and deleted legitimate find logs.
  20. Same here. A CO isn't complicit because they let the log stand. You or I did not encourage anyone to break the law to find a cache. Whoever was looking for the cache did that on their own volition. Deleting a legitimate log just might upset this person enough to revisit your cache and trash it, thus doubling the damage already done.
  21. I have little experience with the variety of different software platforms (Skype, Zoom, Slack, Facetime, Snapchat, Facebook Live, etc) that could be used for hosting a virtual event, but would any of them be able to support a mass log-in from people around the country/world? As we've seen with trackable codes and puzzle solutions, things get shared on the internet pretty easily and often. If GS would allow virtual events, how long would it be before the event code was shared and hundreds, perhaps thousands, of people were to try to join the event? Most event hosts would probably expect that only the local group of cachers, the same ones that attend most of the local events, would be the ones to attend a virtual event, but it's very possible for a code to be shared and many more people than anticipated would crash the party. Maybe Skype or FB Live or Zoom are robust enough to handle the traffic? Or are there restrictions on how many people could join a live-stream?
  22. That's not correct. There were 40 locations total that were closed. The list can be found here. I do believe that all areas that the DNR maintains (parks, trails, rec areas) have closed their facilities (offices, bathrooms, shelters, etc), but access to the parks themselves, minus these 40 locations closed on April 10th, remain open. There are still plenty of state parks and recreational areas open in Wisconsin. Most of the ones on the list are around the more populated regions of Wisconsin and saw a huge spike in attendance last weekend. While I don't personally agree with closing the parks, as you can use the trails and open areas safely, it's hard to argue against the order when you see pictures of the parking lots full of cars and people in close quarters to each other. The impression that gives off is a bad look, even if everyone is social distancing and following safe practices.
  23. After reading the actual "Safer At Home" order implemented by Wisconsin, I had a change of heart and am going to keep my caches active. If social distancing is followed, there is no reason people cannot go to parks, trails, preserves or just around town and geocaching can be a great way to get out of the house and engage in a low-risk hobby. Just be smart about it. No events, no meet-ups, no group caching, carry gloves and hand sanitizer. If you're worried about the possibility that the virus could be passed along by someone handling a geocache, then look at the map and seek out the caches that haven't been found in six months. There are usually plenty of those to be had and you can breathe easier knowing it didn't come in contact with anyone infected.
  24. With Wisconsin implementing a "Safer at Home" order on Wednesday, March 25th thru April 24th, I will probably disable all my caches and suspend my geocaching until the order is lifted. I'm not particularly concerned with the virus spreading by people handling the container/contents, but this order is trying to discourage all unnecessary travel. Most of my caches are hidden in rural locations/state trails. Getting outside for exercise (walking/running/biking) is still very much encouraged and while I would love to think someone would be willing to still bike/walk/run to get near my caches, I know that most people would drive. So, disabling my caches is a small part in helping to discourage unnecessary travel.
×
×
  • Create New...