Jump to content

niraD

+Premium Members
  • Posts

    14747
  • Joined

  • Last visited

Everything posted by niraD

  1. One of the reasons I like Nokia phones is that they're designed to receive Android upgrades for years, and then to receive security updates after that. Even their least expensive phones come with years of Android upgrades. But yes, except for a phone that I accidentally smashed on a concrete surface, all the phones that I have replaced were older phones that no longer received OS updates, and therefore no longer received app updates. Even if the older versions of the apps still run, they often stop working because they can no longer communicate with the servers. (The idea of maintaining backwards compatibility has fallen out of fashion.)
  2. That's not a "maybe." See Groundspeak's privacy policy and related Help Center section on Account issues and the Help Center section on Privacy Rights for more details. Of course, the fact that it's a legal requirement doesn't make the end result any less absurd.
  3. See also the Help Center article Coordinate formats. In general, geocaching uses degrees and decimal minutes, for example 12 34.567 , which can also be written 12° 34.567' Your other example looks like degrees, minutes, and seconds. But degrees, minutes, and seconds work just the same as hours, minutes, and seconds. So if the decimal part of the minutes is .567 , then to get the number of seconds, you just multiply by 60 (because there are 60 seconds in a minute). With my previous example, .567 * 60 = 34.0 , which is the number of seconds. The degrees and whole minutes don't change, so the equivalent coordinate in degree, minute, and seconds format is 12 34 34.0 , which can also be written 12° 34' 34.0"
  4. Also, the NFC aspect of this proposal seems like a bug, rather than a feature. Tonight, Mrs niraD and I were at an event at a local restaurant. There were at least a couple dozen geocachers there, but we visited with only a few. I wouldn't want automatic logs of everyone who was there just because their devices were within NFC range of mine at some point.
  5. Yes indeed. Yes indeed. Yes indeed.
  6. I treat an AL as zero caches, and have just ignored them (the same way I ignore the QR code game and the "gotta catch 'em all" game). But that's a good idea. I might consider creating a separate account for ALs though.
  7. I've been happy with my Nokia 6.1. When it's time to upgrade it, I'll probably get another Nokia. They have Android smartphones at various price points, but they're all designed with value and future Android upgrades/updates in mind. That depends on your service plan. I've been happy with Metro on their lowest level plan. My wife uses TracFone, and each year, when she buys another 365 days of service, she gets more minutes of call time and GB of data than she uses in a year. I have no idea what Verizon's plans look like now. That depends on the app you use. Even Groundspeak's app can preload PQs, although other apps have made that easier. But the API-based apps that I used to use were no longer being maintained, and Groundspeak changed the API in ways that were not backwards compatible, so those apps stopped working. One of these days, I'll find another API-based app that that I like, but for now I've be getting by with Groundspeak's app.
  8. Except for the NFC aspect, this sounds a lot like the Trackable Name Tags sold at the Groundspeak store.
  9. Well, that depends on what you think the promotion should do... But there are various goals (including some sanctioned by Groundspeak, like one-year streaks) that can limit your geocaching in various ways, depending on how you approach them. As an example, when I was working on my streak, I limited myself to only one cache per day. The only exception I made was when I went geocaching with a group, and we went somewhere I wouldn't normally go. But if I was in a park I visited regularly, then I'd find only one cache and save the rest for future visits. Strictly speaking, a one-year streak doesn't restrict you from finding caches. But on a practical basis, one way you maintain a streak is by not exhausting the supply of available caches, and doing that does restrict you from finding caches.
  10. According to section 2-D of the geocaching.com terms of use, "You agree not to: [...] xxiii. Publish on our websites the solutions, hints, spoilers, or any hidden coordinates for any geocache without consent from the geocache owner." However, here are some general puzzle tips (based in part on a puzzle-solving class event presented by The Rat a while ago): Identify the theme. Check the cache title, the hint, the HTML source, the graphics (including names/URLs), any links (including URLs), whatever is at the posted coordinates, etc. If you can figure out the theme, then you should look for numbering systems that are associated with that theme (zip codes, athletes’ jersey numbers, episode numbers, product codes, etc.). Around here, coordinates will have 15 digits, and will look like "N 35° xx.xxx W 084° xx.xxx". So when I'm solving a nearby puzzle, I look for a group of 15 things, and then I look for ways to get the digits 35xxxxx084xxxxx from them. In general, I look for ways to get the number 35 (or the digits 3 and 5) from something near the beginning of the puzzle, and the number 084 (or the digits 0, 8, and 4) from something near the middle of the puzzle. (Of course, you'll need to adjust this for the coordinates near you.) If you ask the cache owner for a hint, then be sure to mention the approaches you have tried so far, and the results those approaches have yielded. It can also be helpful to work together with others who are trying to solve the same puzzle. Geocaching events are a good place to meet other geocachers; ask around to see if anyone else is trying to solve the same puzzle(s) as you. Other useful resources include: How to solve Mystery Caches (also known as Puzzle Caches) (blog post) Puzzle Solving 101 Series (bookmark list) Calgary Puzzle Solving 101 (bookmark list) Puzzle Shortcuts Series (bookmark list) Solving Puzzle Caches (online article) How Do I Solve All These &#$@! Puzzle Caches? (tutorial-style puzzle cache) Geocaching Toolbox ("All geocaching tools a geocacher needs in one box.") Puzzle FUNdamentals (archived event cache) and the Puzzle FUNdamentals resources on the GeocacheAlaska! education page The GBA's Puzzle Cache FAQ (for puzzle designers, but useful for understanding how puzzle caches work) LANAKI's Classical Cryptography Course How to Puzzle Cache (book)
  11. Be sure to read the guidelines, especially the sections regarding agendas and commercial content. There is additional information about the commercial content guidelines in the Help Center article Commercial guidelines explained.
  12. Have you contacted HQ?
  13. I'm glad you got it sorted out. Hopefully, this will help someone else. Like I said, I haven't used MS Windows for years.
  14. Apparently, Groundspeak considers a GPS Maze to be a form of Event, and therefore, it can take place only on one particular date. But the enforcement of that date isn't completely rigorous, so there are workarounds.
  15. I haven't used MS Windows in years, but a quick search indicates a few things to check: Make sure you've updated Chrome to the latest version. Go to the settings in Chrome, then scroll down and select Advanced. In the System section, toggle the "Use hardware acceleration when available" setting to make sure it is on (button should be blue). Restart Chrome to apply the settings.
  16. FWIW, the Google Translate extension for Chrome allows me to select text, and then a button appears that allows me to get a translation of that text.
  17. The API was introduced in 2011. The first API-based app that I used was Neongeo. Before geocaching.com supported corrected coordinates for puzzle (and other) geocaches, Neongeo supported them via the Personal Cache Note. Unfortunately, like many apps, Neongeo eventually became abandonware. And when Groundspeak changed the API in ways that were not backwards compatible, features of Neongeo stopped working. Eventually I had to switch to a different API-based app.
  18. Well, sure. If you turn off your cell/data connection, you're back to GPS with no assistance from the internet. But phones do have real GPS receivers, and can work without the assistance. And their accuracy in that mode should be fine for geocaching. But the smartphone battery lasts a lot longer when it isn't cranking up the power to the cell/data antenna trying to lock onto a signal that it can just barely pick up deep in the woods. If I'm geocaching somewhere with an unstable cell/data signal, then I switch my phone offline just to preserve its battery.
  19. How do they clog up your map? The saturation guidelines don't apply to EarthCaches because they don't have physical waypoints.
  20. A phone loaded up for offline caching - with a suitable app - will continue working properly in the woods. I don't think arisoft was referring to online vs offline. I think arisoft was referring to areas with poor GPS reception, where a phone (or basic handheld GPS unit) might not get a GPS lock to establish its location with any accuracy, but a better handheld GPS unit ("with a more sensitive antenna") may get a GPS log.
  21. And those logs are part of the geocaching history of the people who have interacted with the original trackables.
  22. You could archive one or more of your caches. Other than that, you need to figure out how to handle the geocache-related email that you get. Part of maintaining your geocaches (as described in the guidelines that you agreed to) is to "Monitor logs for reported problems" and to "Delete logs that appear to be false or inappropriate", so you need to read the logs other geocachers post to your caches.
×
×
  • Create New...