Jump to content

Search the Community

Showing results for '���������������������,��������������������������Talk:PC90��������� ��������� ������ ���������'.

  • Search By Author

Content Type


Forums

  • Geocaching HQ communications
    • Announcements
    • Release Notes
  • General geocaching discussions
    • Getting started
    • How do I...?
    • Geocaching topics
    • Geocache types and additional GPS-based gameplay
  • Adventure Lab® Discussions
    • Play Adventure Lab®
    • Create an Adventure Lab®
  • Community
    • Geocaching Discussions by Country
  • Trackables
    • Travel Bugs
    • Geocoins
  • Bug reports and feature discussions
    • Website
    • Geocaching® iPhone app
    • Geocaching® Android app
  • Geocaching and...
    • GPS/API/technology
    • Education
    • Hiking/backpacking
    • Photography
    • Design

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location

  1. I was trying to use the new search on my phone to look up my recently found caches. I gave it an honest try. I went in to do a couple simple searches. WOW it feels like 3 steps backwards from the old search! First and most importantly: Having only one parameter viewable at a time is extremely inefficient and results in a significant loss in functionality. Let's say I want to find the terrain rating of several caches I found a couple weeks ago. First I click on my link to All Geocache Finds. Now I scroll down (scroll, scroll, scroll) to find the cache from a couple weeks ago. But it's only showing the found date so now I have to click terrain. Click the 3 dots. Click terrain. Now I'm back up at the top again! Scroll, scroll, scroll back down. Finally found it! Now how about the difficulty? Sigh... Click the 3 dots. Click difficulty. Back at the top. Scroll, scroll, scroll. Now when did I find that cache again? Double sigh... A simple task that used to take me seconds now is a huge chore. Here's a sample screenshot that shows JUST terrain on my phone: Also, where's the GC code? How come the GC code is missing on the mobile version, but not on the desktop version? I do, however, like that in the mobile version it does not say "Traditional", "Mystery", etc next to the cache icon. Next, I was surprised that while some caches take up only 2 lines (for both the title and the cache owner), some caches take up a whopping 5 lines! There's also an additional line added to tell me the cache is PREMIUM (6 lines of text are wasted in the screenshot below to tell me the various caches are premium). Talk about inefficient! It doesn't look very good at all, either! On the old search page, the columns were long enough such that the title and cache owner would ALWAYS fit on 2 lines. Next, I think there's a bug: my found date just disappears after some point? And finally, something a little strange, but when I'm at the top of the page, some caches show as 3 lines. But when I scroll down and the title rows freeze to the top, suddenly some of the caches switch to being 4 lines. It almost makes me sad to see how inefficient and buggy this new system is compared to the old search. As a tool with the intended use to be searches of recently found and owned caches, I just don't think the functionality is there.
  2. Well, first of all, to answer your question, of course you log the find. Why wouldn't you? As to the outraged property owner, what did you do to make him mad and why couldn't you resolve it? Did you talk to him or just ignore him? It seems as if you were in the perfect position to resolve his problem, but that requires you immediately accept his position as valid and apologizing profusely on behalf of the geocaching community and trying to understand his position about where his property was and whether the cache is on it. It could just be on his property, or it could be you accessed it through his property even though there was another way to GZ. For all I know, you tried to do all that, and he was just irrationally belligerent, so I'm not accusing you of doing anything wrong, but I think it's important to recognize that even irrationally belligerent is a valid response if the cache was -- or just you were -- really were on his property. As others have mentioned, naturally you'd post an NA in addition to your find unless you work out with the property owner that there really isn't a problem with the cache itself, and even in that case it sounds like the lease you need to post is an NM explaining what needs to be done so that this person's property rights are violated.
  3. Let's talk, you pick the subject. You will get our two cents worth... and take it with a grain of salt... oops, should have said: Open topic about Waymarking.
  4. The old search is still there. They just have to change back the links, talk about an easy fix. Of course that would mean admitting they were wrong.
  5. Sorry for the vague title, I didn't know how else to address this. So, I know there's a lot of talk about Geocaching and YouTube, and there's been a sort of agreement as far as I can tell that as long as you don't really post spoilers about a cache and it's specific location, for the most part all is well. Well, there's a pair of YouTubers whom I occasionally watch called MoreJStu that make all kinds of vlog type videos, several of which have recently included geocaching. At first I had no problem with what they were posting. I figured if it got some more people interested in our hobby, that's great! But then they posted this video today: https://www.youtube.com/watch?v=FEub1s5AXUI There is so much misinformation in it about geocaching that I was nearly yelling at my screen. I think it's okay that they're wanting to share a geocache with the fans, there's nothing wrong with that. Except they show where they pack snacks into the cache and encourage others to come out and trade snacks too. Not only that, but they practically bury the cache. It's one thing to hide it with some foliage, but they literally made a hole to put it in. I'm not here to get them in trouble or anything, but I just hate the fact that they're demonstrating behavior against the rules of Geocaching to their 2.7 million subscribers... They also make it kind of known that in more than one video they usually don't trade swag, only take it. If you look on the comments on their vids, you constantly see things like "Ya'll inspired me to start geocaching!" and "Because of ya'll I'm building a geocache fort!". Which is great, except the majority of their followers are young kids who I know aren't going to read any of the rules before going out and geocaching, which will just create more problems... What are ya'll's thoughts?
  6. Sent my info to Laval K-9: 2.27.21Name received from Laval K-9: 3.6.21Sent my gift: 3.10.21My gift arrived at destination: 3.15.21I received a gift: 4.19.21 I had the surprise of a mission in my mailbox tonight! Thank you Semmels123! The Triceratops coin is impressive and the light up tag is cool! I totally noticed yours when I was doing the Geocache Talk "live coverage" of the Texas Counties Finishers Event. Thanks for all the Kansas and sweet treats too.
  7. Compairing numbers as always - the more the better!? Who is the "better" hider? It is not about the numbers but about many other factors. I "only" have hidden 37 caches in 12 years (plus events which I don't count). My current goal is to hide one (in numbers: 1) cache per year so even less then before. My latest mystery cache took me more than 100 hours of creating and in this time I could have thrown out 100 simple traditionals. So please do not look for the pure numbers if you want to "judge" others. I don't want to compare my overall effort in cache hiding to someone with several 100 hides. And I know that there are great cache owners who created one cache that took them years to build - I don't want to compare with them either. It is not about the numbers but about if you (!) like the caches. And that's subjective, of course, so I don't want to talk about cache quality here (*). :-) Jochen (*) Mine are the best, of course! :-)
  8. And there's the difference. I don't agree with the highlighted statement. Again, we're asking different questions. I agree we're discussing our opinions. I don't pretend to be presenting the only correct answer. But I'm justifying my position, I'm not just pushing one answer. So, for example, please explain why the number you think is better is concrete and meaningful. I think we all agree that all registered geocachers isn't meaningful. I'm using the time period of the last month because it excludes people that have already quit, particularly the fly-by-night phone cachers that everyone loves to complain about. The complaint against that is it cuts out the ardent but occasional geocachers, which I don't deny is a valid concern, but I see absolutely no way to count them concretely. I've also explained why I think I'm interpreting the OP's question as more about boots on the ground and why it seems unlikely they're thinking about people that talk about geocaching without actually looking for geocaches. In other words, I'm discussing our opinions to flesh out what numbers we could actually count and what meaning they'd really have. The observation that we all have different opinions is as obvious as it is unhelpful. What I'd be more interested in are actual ways to count something that would produce a more interesting result, not just people complaining that I'm not including this or that group that they hold close to their hearts.
  9. Each summer I usually host two ice cream socials but haven't hosted one since 2019. I've hosted 16 ice cream socials in the same location, a great homemade ice cream shop nearby. I also enjoy hosting GIFF events, I rent a movie theater out and people donate to help pay for it. I'm in NJ but I get attendees from NJ, NY, PA, and CT regularly. It's a lot of fun. Of my 102 geocache hides, 40 have been events. I've learned that "if you host it, they will come. And talk about geocaching."
  10. Like "child molesters and people who talk at the theater."
  11. Hi, the new system won't upload my fieldnotes at all as in my visits.txt file there are more than a thousand drafts from the recent years and the system tells me that it can't upload more than a 1000 drafts at once and nothing happens. So I conclude that it tries to upload all of them. So probably it is just for the first time as I have never used the new system before (because of that reason!)? That's not very self-explanatory so thank you very much for your information. If I understand you correctly I have to upload an empty visits.txt ONCE to activate the "don't upload drafts before ...." feature and next time using the new system it will only take the newer ones? But if I ever switch back to the old system I have problems again as the systems don't talk to each other? Thanks again. Jochen
  12. I agree that you've pointed out a problem we should consider. It actually never occurred to me before that there was no checking of ALs for overlap, but I suppose that's because there are no rules against overlap, as far as I know. Should there be? I have no idea whether there's any kind of approval process for ALs, but if there isn't should there be? All valid question. The specific example strikes me as a big "meh", though. You friend decided to switch back and forth. More power to him if he finds that the best way. I'd be more inclined to do them one at a time, ignoring any redundancy, and possibly using it to advantage by enjoying the park a second time on another day to do the second AL. I'll certainly concede the example and join you in discussing it. But, in the end, I don't consider this a problem and would have no trouble with the resulting rules and procedures continued to allow overlapping ALs. I'm particularly concerned about forbidding two ALs exploring completely different aspects of the same area. I'd be OK with that if we talk it through and decide to do it, like traditional cache distance requirements, but I'd also want to consider a more EarthCache approach where ALs can be close as long as they don't overlap in subject matter. To me, the only clearly demonstrated problem here is that AL creators have no way to find out about each other so they could avoid such overlaps if they wanted to. Any thoughts about what we can do about that? I have no interest in doing an AL, so I don't know whether there's anything mechanisms already in place that failed in this case.
  13. In response to complaints from community members who want to talk about the souvenir challenge, I've hidden a number of off-topic posts from view.
  14. That's a good question that I can't provide a full answer. Let me just focus on my video and then provide observations from my time out there. I lost count of the number of trips I've made to Nevada and the desert areas of the surrounding states, but at least I've seen a lot. The side road itself was always next to the main road. It's how the sage was cut. The parenthesis curves we turn onto are what I'm wondering about. If these were created by geocachers getting as close to the cache as possible, I wonder why they didn't go right next to the caches. You'd figure people would begin driving even closer to the cache as time went on, yet there wasn't any evidence of that. However, every now and then you might see trucks and campers pulled just as far off the road. The dirt roadsides are also graded every year or two, and you see a lot of tracks from those vehicles. Though it's possible some geocachers might drive over the sage, I'd say geocachers form an insignificant part of the problem as you see quads and offroad vehicles every now and then. And the number of shotgun shell casings and litter that's out there, too... I never did get to do the alien head geoart. I knew it was walking, so the three or four times I was out there, the groups I was with always skipped it because of that. Honestly, it did occur to us to drive it, but then it was followed up with a "you're not supposed to do that" and the conversation ended there. On some other trips, I remember following a power line road and some other roads. Many times, I really wondered why there was a road out here to begin with (prospectors?). Caches tend to follow those roads--you can even see them on satellite imagery. Seriously considering going off road to get closer to caches just never came up. We'd just follow the roads where they led and stop as close as we could while still on the road. That was just what you did. At times, you could tell when one car drove over to a cache. Doing so certainly wouldn't make the clearcut paths you saw in my video, though. And when we saw something like this, we'd just think they were lazy morons who risked tearing up their vehicle or puncturing a tire. Not many caches were that far out there, and those that were a hundred meters distant were just seen as part of the game to walk that final distance. I did get to do the Heart of Mojave Desert geoart (shaped like a Gx) with mondou2 and others. We left the cars in the parking area and walked the distance. There was never talk about driving it and, at the time, I didn't see evidence it had been driven. If I may make a tangent, I remember they were shoving water bottles into backpacks. I walked up, took two bottles and put them in my hiking pants pockets. They looked at me strangely. It was supposed to warm up to 110F (43C) that day and that's all the water I was taking for an eleven mile hike (the outer heart, then I'd be able to guzzle and stock up at the cars again before the inner design). I'm always dehydrated--I still am, while typing this--so the water I take with me is more for emergency purposes instead of normal use. I just don't like having anything on my back or weighing me down. Let's see, then there's Yerington. I guess I've been there about half a dozen times. Larry's caches were usually beside the road, so I didn't see any evidence of offroad driving, unless you want to count if a sage came close to the road. He'd just find a road and put out caches along it. There was the state star series, but we walked that. Sure, there was a way to get off the road, but you had all this sage in the way and it would have been faster just to walk. Other places and power trails, you usually had a berm from people coming by and scraping the road every year. I wanted to do the eagle series, but I knew it was a walking one. Larry told me some people had driven it. I didn't want to do that, so never did find the series. That's fine: there were other things to find. Really, if you want to be critical of cachers' impact upon the desert, I'd suggest instead being critical of all the foot trails cachers make from the car to the cache. It's not major, but you can tell people have walked that way, same as people who have used the desert for other reasons. They don't last--the foot trails, not the other people--which at times is somewhat of a disappointment when you have a few dozen sage bushes to look through and then have to realize it's a small rock pile some thirty feet away. But, in conclusion, I'd say the only ones who can answer this question fully are the cache owners and those first to find the caches. I can only provide my observations and try to make them as unbiased as possible. You're always going to have the inconsiderate people doing stupid stuff. The best we can do is set a proper example.
  15. Actually, that wasn't sarcasm. I didn't know someone had already done that. Thank you for giving me more credit than I deserved. (I don't listen to podcasts, don't read blogs, don't receive Groudspeak's newsletter, don't watch videos, don't read much of the forum except for Wherigo, and am generally out of touch. I just go out and find crap, and that's enough for me. I'd rather play the game than talk, read, listen to, or watch something about it.)
  16. I've done the ET Highway a couple times, Route 66, and other power trails. Here are some answers: Why would you do that? I hope it's with others. Since I'm usually alone, it's a treat being with others. And when you do a thousand or more in a day, you get loopy and everything is funny. The run isn't about the caches anymore. It's about having fun with others--oh, and here's the next cache. But you're also doing it for the numbers. Why numbers matter to someone is a personal reason and changes from cacher to cacher. At first, numbers mattered to me (in 2006) because I wanted to find a lot to demonstrate to others I wouldn't slow them down if they invited me to go caching with them. Later, it became about getting to 10K because it was five digits. Still later, it was about how far I could go. These days, it's about activity level and output. I want to relax and find whatever most of the time during the year, but I still want to average around 5K a year because that's a good level for me. All I need to do to do that is take two or three trips, each a week long, during the year. This forces me to take time off work. Without caching as an excuse, like last year due to the pandemic (and I'd imagine most of this year), I wouldn't take time off work and would instead put in ridiculous amounts of uncompensated overtime. Last year alone, I put in ten weeks of uncompensated overtime. You see? I'll pour a ton of effort into something. If it's caching, I'll get a lot of numbers. If it's work, I'll put in a lot of uncompensated overtime. I'm going to do something because I don't know how to let up and all this time and energy must go somewhere. By the way, I'm the type of person that might not even be able to have fun at Disney. I'd make a list of things to do for an ideal experience. Then, when I'm there, it becomes all about doing that list and some other spontaneous things. When asked if I had a good time, I'd say I accomplished the list, which would have been the whole point. I'll then have to think if I enjoyed myself. I guess I may have, but that was secondary to making sure I did the list. How can you find 1000 caches in a day? That's easy. Line up caches next to a road, make the hides easy, and have the caches be the minimal distance apart. Have two to four people in a car. Start early. When I did the first ET Highway, we started at 4AM and later took a break around 6PM for two and a half hours, then finished just before midnight--but that was the first large power run I was on, so everyone was inexperienced. We could have done better and found more that day. These days, if you're doing a number run, it's normal behavior to stamp logs and swap out the cache with the previous cache. You see that a lot. That behavior should be constrained to caches within the series. I don't like it when people do that for other, non-series caches. If you have two cars, you can leapfrog on a road. The lead car keeps finding the next cache. The trailing car, once it finds a cache, eventually passes the lead car, becoming the lead car, and finds the next caches until it's passed. You keep going like that. I'm okay with doing that because it keeps people together. Some people do what I call "divide and conquer". I was in a car with xxxxxx when yyyyyy called. He was in a neighboring state, said he was doing this other power trail, and asked if they wanted to share finds that day. xxxxxx said sure. The only reason I was fine with that was because I had already found that other series. Other times, a crowd of cachers gather (around twenty) and they split up and find different parts of a series of caches. Since I'm not fine with that, I'm not invited that often for number runs. True story, but I'd better not reveal the names. It's possible to solo a 1000 day, but you'll be exhausted afterward. I did one solo and it destroyed my interest in solo power caching for a few years. I did it because I was in a foul mood that I couldn't find anyone to cache with. I don't consider this an achievement and don't want to talk any more about it because I hated what led up to it and my time doing it. I never want to do that ever again. Am I sure it's possible? Definitely. On one trip, someone in the passenger's seat was bored, so began timing us using a stopwatch. I noticed that and it became a fun game. We'd start the stopwatch the moment the runner was back in the vehicle. The driver would drive to the next cache, the runner would get out and swap caches, then run back to the car. The bad times were around two minutes because the runner and team had trouble noticing the cache. The best times were close to fifty seconds. If you averaged a minute per cache, that's 1,440 in a day. But if the caches were all in obvious spots, the road straight, and you knew what you were doing, you could have some sub-minute times throughout the day. No one finds 1000 caches in a day Yes, they do. Even on my first ET Highway run, we did it. We signed every log with a team name and put each cache back where we found it (no swapping, no stamping). That was not the first and only 1000 day I've had. That said, 1000 days are rare and it takes ideal circumstances to pull off. While it's easier to leapfrog, it's doable with one vehicle. Fox's Number Run Team Role Theory From my observation, the ideal team is four experienced cachers in one vehicle. Here are the different job roles, what they do, and why they matter: Driver: The driver is responsible for navigation to the next cache and targeting the one after while the runner is out of the car. An incompetent driver will not consistently park close to caches, costing the team both time and critical stamina. The driver needs to be good about getting as close to the cache as possible. Also, the driver is responsible for the team's safety. If a runner has to cross to the other side of the car, it should always be around the end of the car not pointing towards the next cache. The driver and runner need to communicate to make sure the runner is safely inside the vehicle. Due to the amount of time required to get back into the vehicle, belt up, and start going forward, the driver should be the last that must get out for a cache. Navigator: The navigator sits in the passenger seat and is responsible for several things. First, the navigator is responsible for being aware of where the team is in the series and how the roads and caches connect on a macro scale. The navigator should prep the driver when a branch is coming up. During the cache run, the navigator is looking out the window, trying to spot the next cache as the vehicle is approaching. If the navigator spots it, that information is relayed to the runner. If the person in reserve is resting, the navigator takes over the role of stamping the logs and making sure the runner has cache. Runner: This is the person who hops out for the cache. Swapping roles should be based upon the runner's stamina, but role swapping should always be done before the runner is fatigued. If the runner cannot find a cache in an agreed-upon time, the reserve cacher or navigator should get out and assist. Once back in the vehicle, the runner communicates to the driver his or her save arrival, then hands the cache to either the reserve cacher or navigator. At times, when we had a van with a door that could stay open, I stood on the threshold and hung on to the roof rack. This gave me a better view of the cache site as we came up. I could also jump off before the vehicle came to a stop, using the vehicle's momentum and saving my stamina. To communicate to the driver I was secure, I stomped my foot when I was ready. Only then did the driver move the vehicle. Safety is a priority. Reserve: The reserve cacher is recovering. During this time, the reserve cacher is responsible for communicating to the runner any pertinent information about the next cache. Either the reserve cacher or the navigator can stamp the cache log, but the reserve cacher should be the one to hand the cache to the runner and take the cache from the runner upon his or her return. The reserve cacher is also responsible for distributing food, water, and equipment to the other team members. If the next cache is on the opposite side of the road, the reserve cacher will be called upon to exit the vehicle and retrieve the cache. For the most part, the reserve cacher's primary purpose is to recover prior to swapping to another role. Make sure everyone takes their turn as a reserve or there's another role that recharges them. During a run, the team should agree how to swap and which roles can be swapped. For example, every half hour or twenty-five caches might be an easy way to keep track of when to swap. Never agree to swap only when a runner is fatigued. The point of swapping is to refresh the team so everyone can cache longer. The swap should happen before anyone in any role is fatigued. If you wait too late, you'll burn through stamina and the team will be more tired than it otherwise would have been. Also, pay attention to who is suited for which role. If someone can't stop very close to caches and constantly needs help, that person should not be put into a driver role. Likewise, if someone has mobility issues, the person would not make for a good runner. I cached with a team whose driver needed a lot of assistance and I personally saw the cost. I was later able to swap to the driver spot and put this theory into action. I saw a massive improvement in energy all around: the navigator got excited, the runner wasn't as tired--it was stark and quite obvious. When it came time for my turn to swap, both the runner and navigator--the original driver was asleep in the reserve spot--both enthusiastically said I should continue driving. I did. Personally, I'm a stellar driver and trip planner, so I need no help when it comes to routing and managing both the macro and micro parts of a route. I'm an above average runner, but I've seen some phenomenal runners. Fox and Numbers I'm excited to reach 100K at some point. I have what I call a bucket list project. Since I've never traveled anywhere except to do geocaching, I've assembled a list of things I've wanted to do but geocaching got in the way of doing. Once I hit 100K, I'll pick two things from this list and do them as celebration. I will, of course, find a dozen or so caches a day during that time, but the entire purpose of those trips will, finally, not be for geocaching. I thought of soliciting ideas from the forum, too. One trip I will take, though, will be to somewhere in Japan to try out some onsens and get some photos of nature. I don't know what I'll do for the other trip yet. All I need to do is have two weeks in Yuma to do 4K or a week and a half in Yuma for 3K and then a week around South Dakota or London, Ontario for 1K or 1500K. But I have to wait for the pandemic to be over, though I'll gladly risk myself if I can find the right person or people to take with me as I seriously don't want to do this alone. The bucket list trips must not be done alone or I might devolve into just caching because it's easier just to go to the next cache and the next one instead of figure out what else there is to do in an area and drag myself over to do it.
  17. They made the choice to talk about their lunch on Facebook. Maybe even limited that online discussion to "friends" (not public). The AGF list is not a choice.
  18. It's because the Wherigo Foundation site is an alternate listing service. It was supposed to demonstrate to Groundspeak what we were intending to do with Wherigo so we could run Wherigo for Groundspeak, free of charge for everyone involved. The other Wherigo player apps and builders are on Groundspeak's ban list because of the same reason: they're an alternate to something else--their PocketPC app and their builder, respectively. Though I worked to get community work officially recognized, those at the top of Groundspeak never communicated any of their verbal support to those enforcing Groundspeak's guidelines. Throughout Wherigo's lifetime, regardless of individual intentions at the company, Groundspeak's apparent attitude has always felt one of apathy and passive hostility towards anyone attempting to make their product more accessible to the community. I coined the term "the Wherigo Foundation is Fight Club". They've always told their reviewers not to allow any mention of the Wherigo Foundation or other non-Groundspeak Wherigo applications in cache listings. It's just that the reviewers aren't consistent with each other that caches in some areas were published and others not. Part of the partnership agreement I was reviewing did state that, if the Wherigo Foundation site were to be discontinued, all cartridge files would be provided to Groundspeak for dispersal to community members. I was planning to do that, anyway, so that was fine. There was one other clause I haven't before talked openly about. Suffice it to say, the way I interpreted it, if I ever walked away from Wherigo and did not transition its running to others, the entire game would come to an end. I did not like that Wherigo would then seem to rely on one person's continued health, existence, and interest. The partnership agreement never panned out because Groundspeak took too long in replying, which further showed their apathy (I'd say nine months, several times, classifies as too long, regardless of how patient you are--while waiting for one such reply, I had a house built and moved into it). An odd quirk to all this is this Wherigo forum. Why can we openly talk about these applications? The answer is a combination of me and Groundspeak's apathy. Back when matejcik and charlenni first presented their applications, the forum rule was that moderators needed to clear through Groundspeak talk of new applications. So, as the moderator, I hid the threads and sought approval. Groundspeak did not reply for a month, so I unhid the thread. When that second application was announced, I hid the thread again and asked Groundspeak. I again didn't hear a reply and unhid the thread. Later, I did get a reply, saying it was fine and that there wasn't anyone at Groundspeak who could speak for authorizing these, so that's why it took so long. I asked, then, for something no other moderator has: the authority to make these decisions on my own. It was granted. Ever since then, so long as something wasn't commercial, I allowed it. Now, mind you, Groundspeak's employees have definitely changed since then, so no one there remembers that this responsibility was delegated, so would likely take it away. Another odd footnote is Wherigo\\kit. I am able to use Groundspeak's API for authentication, which does require approval and a review. More recently, when I had to submit an updated overview of this application, I was asked by someone at Groundspeak if I wanted Kit to appear in the list of official Groundspeak partners. I guffawed, pointing out that Groundspeak's reviewers do not allow caches to be published if they mention Kit, the Wherigo Foundation, or any other application, so listing Kit as an official Groundspeak partner would thoroughly confuse the situation, so Groundspeak should really consider its stance on the matter. This was about two years ago. Finally, something that irritates me. Groundspeak allows cachers to mention GSAK and Project GC in their cache listings. Both are commercial applications--GSAK was up until recently and Project GC pushes a subscription model. Groundspeak also allows mention of other commercial applications in cache listings. But, yet, when it comes to everything the community has done to help Groundspeak with Wherigo--and everything we have has always been free, with the individual developer shouldering 100% of the continued cost--Groundspeak has this as their official position. And, believe me, there are ongoing costs. I average about $200/month for hosting, storage, SSL/TLS license, and domain registrations between Kit, the Wherigo Foundation site, DevOps/TFS, and the staging areas I use when publishing. I could decrease the cost by doing a shared hosting plan, I suppose. I suppose I could have still continued to create things. But there comes a time when one needs a solid support group to provide feedback and motivation. I don't have that. And you'd figure people in my own area would be really supportive of my endeavors, be it Wherigo or having found almost 95K caches. They're not. There's a distinct anti-Wherigo feeling in my area. There have been some that would like it if I quit geocaching altogether. So, no support there. One can continue only so long against the flow and apathy before exhausting oneself. So, later, my job became the beneficiary of some of my free time. I worked uncompensated overtime 300 hours last year and 400 hours this year (and no time off). You'd think they'd be grateful, but instead I get managers telling me they're not asking me to work extra hours and they're apathetic about all the things I'm doing to fix their aging application single-handedly. No encouragement, no support, no appreciation from there. Sigh. So, anyway, that's my view on the matter. There are always other sides to it, though I've tried to be neutral.
  19. Well, I did find that Costco has the 64x for $199 which is a great price. Most of the 60csx's are going for $130-150 on ebay, so I may as well spend a little more and get a new one! I did use my new phone and Locus to find a cache today, and it was one I'd looked for twice before, so I was happy to finally find it. The Pixel 4a 5G works well even in the trees. My old phone, a Samsung Galaxy J7 Crown (a cheap straight talk version) did not, and I had been pretty far off before. Thanks again everyone for all the discussion and assistance. My daughter and I are looking forward to doing more caching this year and I think we're already off to a good start. Oh, and one of the goals this year: dispersed camping in the Olympic National Forest. And wouldn't you know, several spots are marked in Locus, I'm guessing by others users. Very cool, and worth the cost of entry by itself!
  20. Wait a minute. It says "that negatively affects society" and not "that made the society change something". A disaster doesn't necessarily have the effect that the society changes something. What do they do after an earthquake? The accident negatively affected society by killing several people. And maybe they haven't changed traffic patterns (as if that would stop a drunken driver), but at least they created that memorial to maybe make some people think before they enter their car with alcohol in their blood. Edited to add: It's not that easy to find photos of these memorials for Europeans (the provided link doesn't work here), but finally I saw them in a video I found. Now that I have seen them, I would also suggest the Citizen Memorial category, because the plaques don't even mention the accident, but instead talk about the killed persons.
  21. I ran into some technical issues when I tried to post this before so this may be a duplicate post. Please ignore and remove this one if it is. Thanks. ================================ Hi there - I'm trying to put out a cache that has a picture but I want the picture to be a surprise so that people only see it when they click on the right link. However when I upload the picture to the actual cache, it shows up in the gallery and is listed at the bottom of the description as well. I don't want it to be visible there (or anywhere else ideally). Is there a "official" solution to hiding the picture somehow? As far as I know you're not allowed to use 3rd party hosting sites any more so I didn't even bother trying. I've also read some forum posts that talk about adding the picture to an archived cache instead and then using a link for it in my new cache but my concern is the picture is still "visible" in that archived cache. People could come across it accidentally there (or maybe on purpose). Is there any other options out there or is there a setting somewhere that hides pictures from the gallery and the cache description listing? I was thinking about maybe loading the picture into my unpublished archived cache because, as far as I know, no one else can see those caches, but I can't edit those archived caches to add any pictures. Plus I'm not sure if the website will allow other people to see those pictures anyways. ie I'd be able to see the picture because I have rights or permissions to my unpublished caches but no one else does. I also considered loading pictures via a Reviewer Note on my new cache and linking to them from there. Those Reviewer Notes get "removed" when the cache is published but do any pictures associated to those logs get deleted too? Or would the links keep working? It's hard to test all these things out obviously so I'm hoping someone knows the more official way of doing this. I don't want to implement something that may suddenly break a few years later either when GS changes a policy, like the 3rd party hosting thing. Any help or suggestions would be greatly appreciated. Thanks in advance.
  22. Amazing. Just as we talk about it in this thread, I've got another finder in the process of working through it! You brought the cache some good luck by starting the thread! Will be interesting to see his log. Stage 4 is pretty easy since the distances really do call for driving, though it can certainly be done easily enough on a bicycle, so there's that to sort out if pedaling, I guess. As for power, it's a secret! Stage one is a particular power hog due to distance between xmitter and posted coordinates, and propagation requirements. The others employ high gain (very directional) antenna systems.
  23. When I travel, it would be great if I could get the GPS to talk to my android tablet. I got an adapter cord so I could hook the two together, but if I try to send way points to the GPS I get "your browser is not compatible" and I've tried all three browsers on my tablet. Should I give up this dream, or is there a way to do it?
  24. No, it's the same issue that I described previously. Comcast is now throttling Weekly Mailer messages we attempt to send by deferment, so our server keeps retrying until the message is accepted or expired. In this case, it took ~4 days. Here are the logs: Sep 30 13:40:36 signal2 postfix/error[18592]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=0.1, delays=0.1/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta34.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 14:21:55 signal2 postfix/error[27076]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=2478, delays=2478/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Sep 30 15:15:28 signal2 postfix/error[26069]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=5692, delays=5692/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta10.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 17:31:19 signal2 postfix/error[21426]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=13842, delays=13842/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta19.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 21:50:24 signal2 postfix/error[21488]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=29388, delays=29388/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta25.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 02:20:11 signal2 postfix/error[17888]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=45575, delays=45575/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta25.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 06:50:08 signal2 postfix/error[14401]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=61771, delays=61767/4.3/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta28.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 11:20:24 signal2 postfix/error[10233]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=77988, delays=77967/21/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta09.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 15:50:18 signal2 postfix/error[5719]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=94181, delays=94167/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta30.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 20:20:06 signal2 postfix/error[1014]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=110369, delays=110367/2.6/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta29.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 00:50:09 signal2 postfix/error[29149]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=126572, delays=126572/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta12.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 05:20:20 signal2 postfix/error[24714]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=142783, delays=142764/19/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta32.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 09:50:20 signal2 postfix/error[20450]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=158983, delays=158965/19/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta27.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 14:20:05 signal2 postfix/error[15686]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=175169, delays=175165/3.9/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta02.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 18:50:05 signal2 postfix/error[11213]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=191369, delays=191365/4/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta21.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 23:20:32 signal2 postfix/error[5842]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=207596, delays=207564/32/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta26.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 03:50:18 signal2 postfix/error[1119]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=223782, delays=223765/17/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta12.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 08:20:09 signal2 postfix/error[28593]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=239973, delays=239966/7/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta38.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 12:50:08 signal2 postfix/error[23322]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=256172, delays=256167/4.6/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta17.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 17:20:18 signal2 postfix/error[18820]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=272382, delays=272367/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta08.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 21:50:19 signal2 postfix/smtp[13687]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=mx1.comcast.net[68.87.26.147]:25, delay=288583, delays=288567/15/0.3/0, dsn=4.0.0, status=deferred (host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta18.westchester.pa.mail.comcast.net comcast Try again later) Oct 4 02:20:12 signal2 postfix/smtp[8287]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=mx1.comcast.net[68.87.26.147]:25, delay=304776, delays=304768/6.3/0.3/0.7, dsn=2.0.0, status=sent (250 2.0.0 YxL81m02s3RP4Bm0QxL95o mail accepted for delivery) And I still don't get one. Yours is still in queue for delivery: Sep 30 14:23:56 signal2 postfix/error[17402]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=0.1, delays=0.1/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Sep 30 17:01:53 signal2 postfix/error[20668]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=9478, delays=9478/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta14.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 19:48:30 signal2 postfix/error[10666]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=19475, delays=19475/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta06.emeryville.ca.mail.comcast.net comcast Try again later) Sep 30 23:50:09 signal2 postfix/error[26238]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=33974, delays=33974/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta21.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 04:20:05 signal2 postfix/error[22530]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=50169, delays=50169/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 08:50:11 signal2 postfix/error[18967]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=66376, delays=66367/8.7/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta35.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 13:20:23 signal2 postfix/error[14592]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=82587, delays=82569/18/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta17.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 17:50:19 signal2 postfix/error[10261]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=98784, delays=98769/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta18.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 22:20:17 signal2 postfix/error[5594]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=114981, delays=114969/13/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta06.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 02:50:19 signal2 postfix/error[1345]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=131184, delays=131171/12/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta30.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 07:20:30 signal2 postfix/error[29898]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=147394, delays=147371/23/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta37.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 11:50:23 signal2 postfix/error[25103]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=163587, delays=163571/17/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta13.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 16:20:22 signal2 postfix/error[20394]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=179787, delays=179771/16/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.COMCAST.NET[68.87.26.147] refused to talk to me: 421 imta38.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 20:50:21 signal2 postfix/error[15742]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=195986, delays=195971/14/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta15.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 01:20:22 signal2 postfix/error[10582]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=212186, delays=212171/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta20.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 05:50:22 signal2 postfix/error[5603]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=228386, delays=228370/16/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 10:20:31 signal2 postfix/error[832]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=244595, delays=244572/23/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta15.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 14:50:28 signal2 postfix/error[28274]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=260792, delays=260773/19/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta23.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 19:20:24 signal2 postfix/error[23125]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=276989, delays=276974/14/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta24.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 23:50:26 signal2 postfix/error[18230]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=293191, delays=293174/16/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta03.emeryville.ca.mail.comcast.net comcast Try again later) Oct 4 04:20:30 signal2 postfix/error[12972]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=309394, delays=309376/18/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta01.westchester.pa.mail.comcast.net comcast Try again later) Oct 4 08:50:36 signal2 postfix/error[8163]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=325600, delays=325579/22/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta16.westchester.pa.mail.comcast.net comcast Try again later) Oct 4 13:20:35 signal2 postfix/error[2929]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=341800, delays=341778/22/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta24.westchester.pa.mail.comcast.net comcast Try again later)
  25. As of Thursday, stats showed that there were 7 more geocaches with the Challenge Cache attribute than mystery caches with "challenge" in the title. That spread has reduced month over month (we track it every month on the Challenge Talk podcast) and this is the closest they've been yet; but it shows that there are either non-challenge caches incorrectly tagged with the attribute, or valid challenge caches without "challenge" in the title.
×
×
  • Create New...