Jump to content

frumiousb

+Premium Members
  • Posts

    33
  • Joined

  • Last visited

Everything posted by frumiousb

  1. It's still a problem. Geocaching.com via Chrome on Android.
  2. I'd like to address cache height. There are a lot of tall placers. That's fine. But not everyone is tall. When tall placers put caches at what they think is their eye level (or above!) and then rate it a T1.5 because it's like 50' from parking in a flat park and is just into the treeline from grass, it sounds great - but 6.5' or 7' up still might be completely unreachable for someone 5' tall or shorter. And they're often tethered, so it's not like you can use a grabber to get it down and then put it back. If there's nothing nearby to stand on and it's not on a tree that can be climbed easily (like up in a sign, or tethered to an overhead branch near the tree trunk), shorter people simply can't reach some of these. So tall folks, either mention the height in your descriptions or say "folks [specific height] or shorter will likely need an assist". Better yet, don't rate them T1.5. The "average" cacher is not 6'+ tall except maybe in the Netherlands. Here's a specific example - a few logs back. And mine below theirs. This one was at least not solidly tethered, so it was (barely) removable and replaceable. Several other finders mention having trouble reaching it or that being tall helped. https://www.geocaching.com/geocache/GC9KFDG_geoint
  3. Ugh. Was concerned it was something like that. Lose-loae for me Thanks for the explanation.
  4. Starting somewhat recently, not sure when, showing my lists on the map shows the projection completely wrong vertically. The vertical direction is stretched and the dots show up in the wrong place or the dots in the right place or the map is so wrong that they're not the correct spot. For example: Screencap shows my "Avenge DNF" list - should be going across the USA but instead seems to be going across Mexico and in the ocean. Chrome on Android Pixel 6 Pro.
  5. I have been trying for hours this afternoon to download several cartridges from the same series from the same creator. Whereyougo correctly downloaded only two of them out of four that I tried today. It said it downloaded the others but didn't open them within the app. Doesn't seem to be any way to get them to come up because they don't show up on the list. So I paid the money to download Geooh. Tried to download the cartridges in there. It says I can't download because I don't have permission for that directory or something. I can't figure out how to get it to use the directory that whereyougo uses so that I can see the same list of the ones I've already downloaded. Screencaps attached showing where WhereYouGo has saved the cartridge files and of the Geooh error Grrrrrrrr
  6. Booooooo to this >:( Try harder. Do you get player permission for pages getting cached or crawled on the web?
  7. Similarly frustrating: Challenge caches that desperately need a checker, often because they require you to tally points for a long list of caches that you may or may not have found, which requires clicking on every one in the list that you aren't 100% sure you *haven't* found.
  8. In Chrome, foreign-language pages are generally automatically translated for me (by Google Translate, presumably) - except on geocaching.com. There seems to be some code within cache pages that keeps Chrome from asking if I want them to be translated. Example: https://www.geocaching.com/geocache/GC7T345 (in Polish)
  9. You aren't supposed to leave food or candy because the smell attracts critters AND sometimes the stuff rots or melts. Band-aids and face masks don't melt or rot or attract critters, unless they have some yummy smell I haven't noticed before. Maybe the Band-aids wouldn't be a good idea in heat if the Band-aids are the kind with a gel on them. I haven't left face masks yet (and if I did, they'd be in their own bags). I have left Band-aids, a number of times. I get cuts all the time while caching and assume other people do too. Sometimes you don't have one with you or you use up your supply and it's nice to replenish on the road. But I either just leave them or swap for something minimal, like pennies or tiny plastic dinos. Now, if you're swapping a single Band-aid for a stuffed animal, Houston, we have a problem.
  10. Hubby got me one of these - a shorter one, I think - so I could get a specific cache I'd had my eye on. Very cool ladder. Watch your fingers when collapsing it!
  11. I'm that person. Sometimes I thought I clicked "favorite this" for the cache but didn't, and may or may not notice the oversight later. Sometimes I want to, then find out I'm out (I tend to award ALL of my FPs), and then when I do have an available FP again I have to remember to go back to find the log where I said I'd favorite it. But I can't always remember which one it is, especially back when I was streaking and getting at least one every day, or when I was on a trip, and searching old logs isn't easy. I do (or did) have GSAK but it doesn't always work on my Mac, so my GSAK list is VERY old. Instead of the CO sending a reminder (which could look needy), I'd like to see the *site* implement reminders. Have {FP} or [FP] (case-insensitive) be a tag you can put in your logs. Once a day, week, month, whatever (I'm thinking month, to give folks time to earn enough FPs to cover the ones they'd like to give), GC - or Project-GC, whoever wants to do this - runs a script that compares this tag with whether you really did leave a FP for that cache or not. If you did, fine; you get an EOMonth summary of any/all caches you've favorited. If not, you get a list of the ones that you tagged but didn't favorite with a suggestion to either add the FP (if you have one available) or to remove the tag. Monthly note to cachers could look something like this (with the GC# linked to your log on each cache page): ~~~ frumiousb's favorite caches for August 2020 ~~~ You logged these caches as favorites and awarded each an FP: GCABCDEF1 - D/T - name - placer - location your log: [...] GCABCDEF3 - D/T - name - placer - location your log: [...] GCABCDEF7 - D/T - name - placer - location your log: [...] You logged these caches as favorites but did not award them an FP (yet?). Click on the GC# to go to your log if you want to award an FP now or edit your log to remove the tag. GCABCDEF2 - D/T - name - placer - location your log: [...] GCABCDEF5 - D/T - name - placer - location your log: [...] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --Pickypicky
  12. My thoughts exactly. Most of the old virtuals are historic (at large historic sites, homes, local history signs, cemeteries, monuments, etc.) and very interesting. In fact, they're generally my favorite caches. To paraphrase the real estate ad, "I didn't even know XYZ was there." Often they're in parks or other places where you can't put a physical cache. They are disappearing as the older cachers who placed them retire from playing, pull back from playing, forget how to access their accounts over the years, or worst, die. Plus most of them are OLD. Archiving them and/or not letting them be adopted makes it harder to fill in old months for JASMER.
  13. OK, I've heard there are a few other listing sites, although if it's listed on geocaching.com one would think it's supposed to be a cache on geocaching.com. What "other uses" besides letterboxing? And again, what about virtuals that the CO no longer responds about? It's not like anyone can just place a new virtual nowadays.
  14. Some of that, sure, but there are some really old ones that are still going just fine - or that were archived because of an inactive CO but are still there and are in perfectly good shape, some of them being virtuals - that should keep going as-is. As far as recording the ownership, the code could track things differently so that formerly owned caches show up on the original CO's page with some special icon or color. There are some really old caches that can't seem to be adopted out because of the way the adoption rules are, and it'd be a shame to lose those oldies. As far as changing adopted caches - no, you can't stop someone from doing so but generally it's an honor code thing to leave it as close to the original as possible, just like it's an honor code thing to actually log finds and DNFs, to do maintenance when you can if you come across a cache that needs a new bag or log, and so forth.
  15. I'm frustrated that active cachers can't adopt caches (physical OR virtual) that have basically been abandoned by owners who are long-inactive or even known to be deceased. I wrote in about it; official response was that the caches belong to the CO and can't be adopted out without their permission. And if the CO is dead, you're supposed to somehow contact their executor or some such and get a copy of the death certificate!!! That's an awfully high bar. There should be a timeout period for inactive and unresponsive but possibly still alive COs of ...I don't know, a year? Year and a half? Two? Three? before a viable cache becomes fair game for adoption by active locals. For known-dead COs, their caches should be adoptable after a few months of trying to contact their family. Similarly frustrating: that certain caches can't or won't be unarchived even if they're still (or again) perfectly findable. Here's one such that I just came across: https://www.geocaching.com/geocache/GCHVCH_douglas-18-trappers-trail
  16. Fabulous place to have one! I shiver just looking at their winter feed. Would love to get up there sometime for the webcam - in their summer.
  17. Exactly - all of these. Excellent suggestion to rename "Micro" to "Nano to Micro". It's not just an Aussi problem. Huge problem here in the USA as well.
  18. Hi - just saw this now. No, haven't looked into much of anything via Waymarking; still trying to figure out how that works. Hubby has the electric car and I'm the only one caching, so it would kind of need to be driven the other way most of the time. But I'll check it out, so thanks
  19. We now have one vehicle that plugs in, though it's not fully electric. I suggested we take it out for a drive today and find a cache wherever we end up (it's really hot and muggy and I don't want to do a long anything). Hubby asked if we could go find a cache near a charging station. I don't know of any and that isn't an attribute yet AFAIK. Googled - and found one on the other end of the country, in Washington state. If you know of any, especially in the greater DC Metro area and particularly NoVA down to Richmond, please share that info here. Thanks!
  20. Trying this now. There are four different choices for cartridge type, three types of GPSes (I just use the GPS features and the geocaching apps on my Android phone) and PocketPC. Guess I'll choose that last one... Ooof. Now I have to get it to some other directory because it isn't where Wherigo is looking. I have some other things I need to work on today; will try to get back to this one another time.
  21. I'm having this same problem on my Android. See the other post I just made about it:
  22. I've tried a number of times to get WhereYouGo to download the Joe Pickett Wherigo cartridge to my Android phone. No luck. Always get a download error. Saw this thread last night after some searching, so I downloaded WhereiGeooh*. It won't download the cartridge either. I manually typed in my geocaching.com username and password. I've gone to the Wherigo.com website and done the same and can log in there, but can't download the cartridges to my phone. Advice would be very welcome here. * as far as the app itself: WhereiGeooh seems to have some nice features but it is horribly slow to do anything: show a map, show details for a cache, show a log. I'm also not happy with how many permissions I had to allow it (photos, files, media, etc. in addition to location).
  23. Good for you! I didn't start caching in earnest until the beginning of this year, when I started going up to a few days a week. I didn't go every day until something like late March so I have a long ways to go.
  24. CAVinoGal - I'm similarly doing a streak (trying for 366 - am in the low-to-mid-100s right now), so Hidden Creatures is requiring a lot of extra effort to NOT grab caches that I might want/need during horrible weather days over the winter or sick days.
×
×
  • Create New...