Jump to content

Search the Community

Showing results for '부천콜걸경기출장안마【TALK:za32】'.


Didn't find what you were looking for? Try searching for:


More search options

  • Search By Author

Content Type


Forums

  • Geocaching HQ Communications
    • Announcements
    • Release Notes
    • User Insights
  • General Geocaching Discussions
    • Getting Started
    • How Do I...?
    • Geocaching Topics
    • Geocache Types and Additional GPS Based Gameplay
  • 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

Found 27836 results

  1. Bingo! Now go join Tennis Courts, talk to the NW History Buff and see what you can get done there. Serving as an officer there would serve as a good "introductory experience" to category ownership. Keith
  2. In that thread it turns out that many of those COs were not actually maintaining those caches. They had strings of DNFs, NMs, no OMs, reviewer notes and disables. I see that you were rewarded a Virtual. And looking at your stats I'd say well deserved. You have a reasonable amount of hides that you look after without getting a reviewer involved. You even check your caches just to check if they're still in good order. The anti-algorithm talk and 'why don't I get to own a virtual' protests spoke volumes.
  3. BAD NEWS about the Myncaster station. I stopped by there today and was able to talk with a farmer just north of it. What appears on satellite views, in the vicinity of where the station once was, is an old barn & hay shed. The Myncaster station was moved north and west from there some time ago and has since been destroyed. SOB, SOB! Keith
  4. You see, that's why analogy's don't really work all that well as arguments. Money = FP's breaks down because you are spending any money given by an employer (even investing is giving that money to someone else to "hold" for you) which you don't do with FP's. Employee of the Month is handled very differently with each list. So trying to force one thing (FP's) into another model (money) only works just so far. So let's quit arguing about a poor analogy, talk about FP's and goals in "awarding" or "collecting" them.
  5. First off I'm not picking on this person, not going to say what cache it is or who placed it, but I did want to talk about it and see if you had any similar experiences. Was alerted of a geocache recently published near me last night so I went out but was unable to find it. Sent the OP a message asking for a hint, and they directed me pretty far from the coordinates, about 20-30 feet away. I went back this morning with the hint and lo and behold tossed in the bushes pretty far away was just a simple GLAD container with 2 pieces of blank scrap paper, a clothespin, and a rubber eraser. FTF, hooray? I checked out their profile and this person joined only a couple weeks ago with 3 finds and 3 hides. I understand not everyone has money to spend on official geocaching containers and crazy swag, and in a cute way this is basically geocaching at its essence in a little Tupperware container, but would any of you been happy to find this after searching 2 different days for a total of maybe an hour and a half? There's a reason why Geocaching recommends you find something like 20 caches before hiding your own. Honestly when I saw it in the bush I thought it was some random trash someone threw out of their car window as they passed by, I know you've all seen the type of stuff I'm referring to while hunting. The placement was also super strange. I'm going to message the OP and mention that there is a big tree absolutely perfect for hiding this in about 20 feet up the trail, with lots of holes and hiding spots. Tossed in a random bush by the side of the road way off the coordinates is not fun to find for anyone. Anyway, hopefully I can work with this new player to maybe help them and make this cache better, and was wondering if you guys have any similar stories? Have any worse experiences? All things considered it's not THAT bad, so I know you guys must have some horror stories worth sharing.
  6. My first Geocaching experience was in 2008, right when the activity had gained a lot of traction. One of my extended relatives asked me if I had heard of Geocaching. I forget the exact explanation he used, but I was very intrigued. My cousins and I hopped in the car and joined the search with my relative. I didn't find any of the caches (they were all micros), but the people with me did. I signed my name and the rest is history. I think the best way to get muggles into it is to talk about it. I usually bring up the names of trails I walk and mention Geocaching. They either give me a puzzled look or a "Yeah I've heard about it." Also, there is a trend on Tik Tok that I learned of recently, so a lot of younger people are being introduced to it that way. Last week, I found a cache in front of some muggles. They asked what I was doing and I explained Geocaching to them. They responded positively, so I might have helped a "wizard" discover themselves! My favorite is to just ask a muggle if they want to go Geocaching with me. I've done this maybe once and it was a good time.
  7. 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)
  8. This makes no sense. FPs are used in so many different ways for so many different reasons that if you're concerned about what they mean for others, it means you probably shouldn't use them at all as there's no way you can use your FP in a manner that means the same for everyone else. You're basically saying that someone who gives a FP for a FTF (it certainly happens) or gives a FP to the cache because they know the CO (this happens as well) should factor into your decision to award a FP the same way someone who gives a FP for an amazing location or a FP for a rewarding caching experience from start to end. How will you ever be able to meet the expectation for every reason a FP is awarded? You earned the FP and it's yours to give as you deem warranted. Why should someone else's thoughts about what they believe a FP means factor into your decision to award your FP to a cache? Cerberus provided the appropriate link to rebut this. Some cachers did (and still do) use it that way but that was never the overriding intent. It was only an addition that allowed cachers to add FPs to caches for whatever reason they felt like awarding one. I've added them for a cool creative container, the amazing location, the total experience from start to finish, for a cache placed in remembrance of a caching friend, for the opportunity to talk to an Amish gentleman in a cemetery and learn the history of the church and the community, and for other reasons. I guarantee that many cachers wouldn't have found the cache where I was talking to the Amish man a "good" cache. It was just a micro container along a fence line in a cemetery. The experience I had was what made that cache FP worthy. If I were ever over in @barefootjeff's neck of the woods, you can bet I'd look at the caches he's given FPs to because we appear to have similar tastes in cache experiences. I do use FPs to help filter caches when going to a new area for a family vacation. Caches that I ordinarily might remove from my list stay on it due to the number of FPs it has accrued. Sometimes the cache turns out to be worth it while other times it is a dud of a cache. They will never guarantee a good/great experience since they're awarded for too many various reasons to be consistent. However, the odds are usually a bit better than just some randomly filtered out caches with far less (or none) FPs.
  9. Let's set up a long term thread that we can all talk about caching in and around San Diego County.
  10. I don't think there's a need to skip over the identity of the person/category leader in question here. He's not an ogre, nor a mean and vindictive or vengeful person, just cantankerous, as many of us are becoming. For some reason he's just unwilling to come and say "Hi". I feel no antipathy toward him and I suspect that most people here feel likewise. They'd rather just have the opportunity to understand his point of view. I believe he's here, listening and watching right now. What say Possum Man? Could you come and talk to these people? Keith Addendum: OOPS!! I have been apprised that the Possum Man may not "come and talk to these people". Displaying my ignorance here. My apologies to all, including the Possum Man. OH CRAP - I've done it again. How do I get rid of the stuff below?!?!
  11. Check the list in my post above from Feb 17. It is from the same source. I watch both to see if any new ones are added. It's all "GPS". Different countries put different names on their own systems, though. (g.e., EU = Galileo, Russia = GLONASS, China = BeiDou, etc). It's a competitive environment. When we're talking about L5, it's strictly a US issue. The U.S. govt is still calling the L5 signals from Block III 'pre-operational' and won't be considered fully operational until 24 of the Block III birds are up and broadcasting. That isn't anticipated for some years. Not sure when Lockheed-Martin will be done getting the last of the IIIC units into orbit. Looks like SVN 74 (PRN 4) is up and running and healthy since mid-January 2020. That said, I fully expect nav companies to use any 'healthy' L5 signals to augment what's already in the air long before all 24 are up. In order to deal with things like Galileo, a receiver has to be looking in the right place. While we've been talking about L1/L2/L5, you have to then look at Galileo as E1, E5/E5a/E5b, and E6. Whether the chip maker covers the whole spread varies between manufacturers and chips within their families. All of them talk about civilian accuracy in the 3m range.
  12. Talk about an EVIL hide! I read in the news about the astronaut who dove down to the deepest accessible area on the ocean floor. Who knows, perhaps our diving technology will improve and sunken shipwrecks will become Wherigos. A really neat Earthcache would be the volcanic vents on the ocean floor. I couldn't imagine placing physical containers in shipwrecks, WAY too dangerous/unethical in some cases.
  13. The OP is clearly asking about the "unofficial GeoTour" meaning of "GeoTrail," so let's talk about that.
  14. i have a problem and not sure how to fix it . i have a old lap top on vista and runs an old version of chrome and my gps does communicate ok with it. but my windows7 based pc used to comunicate to the gps then chrome and firefox and others change things to make the it safer to use the web .i belive since then i plug the gps in and the computer does not even know its there, i have down loaded the plugin from garmin still no go its getting to a point i belive its the windows7 based pc and chrome that have caused the connection problem , but how do i sort it please help in easy to understand computer garble. cheers steve
  15. I am having the same issues as the ones posted above. I have contacted Groundspeak and have received the same answer back as the others. I have contacted my internet provider and also contacted my carrier AT&T which I spent nearly an hour on the phone with. The one I was talking to even went higher up the food chain to no advail. They said the only way they could really tell why i am not receiving my text notifications would be to follow a text from start to finish but I don’t have a clue how to give them an origin for a text that I am no longer getting. It seems like they need to talk to someone at Groundspeak to follow the transaction from start to finish. If you will furnish me that number I would be glad to contact AT&T and give it to them.
  16. I've got a great idea - Let's put out a new category in peer review on a US holiday weekend so that hardly any US waymarkers can look at it! Nice. It's also another great idea to never have had it discussed in the forums. You aren't really requiring photos - you're saying screengrabs are okay. This is a violation of Groundspeak terms of service if those "screengrabs" happen to belong to someone else on another platform like Facebook, Twitter, etc., where the original photographer and the platform hold a copyright. You have to agree to terms of service for each waymark you post and violating that terms of service can get the waymarker who "screengrabs" the picture of the rooftop garden in trouble with Groundspeak and with the copyright holder. Groundspeak Terms of Service You agree not to: "viii - Upload, post, transmit, or otherwise distribute any content that infringes any patent, trademark, trade secret, copyright or other intellectual property, or proprietary rights of any person, including without limitation under any privacy or publicity rights. xi - Violate any applicable local, state, national, or international law." How are people supposed to visit these, especially if they are private rooftop gardens? There is no mention of this in the writeup? What kind of long description are you requiring? Where does one get the coordinates for the garden, especially for a private one that they cannot physically visit, but can only take a picture from afar? What about trespassing and voyeur laws, especially for these private gardens where you would be taking photo from locations outside the garden? If you are shooting from another location, you could be violating privacy laws, which I know for a fact a very strict in California and are very strict in Europe. With that said, that would be a violation of, again, Terms of Service 11. You also speak of playgrounds - why both? Again, people who own these are going to have SERIOUS issues of people taking long range photos of their kids on a private playground. This category isn't well thought-out; it is not well written-out; and frankly, and it definitely has the possibility of being downright illegal. This is why you should always bring these new category ideas to the Forums first. Talk to me on the above, clear up the concerns. There is a hole where this category might fill, possibly, but how can you document these without violating the owners privacy and, just as importantly, how could someone visit these waymarks? I have published the above as my response in peer review.
  17. My assumption was that reviewers might only do this when they happen to know the exact location, e.g. probably not all that often. I don't really know how much responsibility any individual reviewer has to enforce any particular rule, so I perhaps wouldn't go there. Well no, I was assuming the multi was blocking large area, as that was the premise. (somewhere between a single waypoint and an entire town) Addressed in my premise: "unobtainable to most cachers for a reason that isn't related to the location (e.g. a run-of-the-mill T5 tree climb near a waterfall) ". There's also been talk of "dumbing down" things, which I haven't perhaps properly addressed after that premise, but I did mean unobtainable in a fairly literal sense here. The argument wasn't for popularity at all costs, and that wouldn't be an argument I could ever see myself supporting. Take your example puzzle cache, almost anyone can go look some letters in a sign if they choose to; it's just that some don't want to. But the skill and gear for T5 climbing or scuba diving, or the intelligence/domain-specific knowledge required for certain types of puzzle present a barrier that can't be overcome by simple choice. In fact there's probably a very finite set of people in any area that can ever do those caches. The few hour hikes and boat caches that don't require an actual seaworthy boat and skill fall somewhere in the grey area in my mind. I'm still healthy enough to do that kind of thing fairly effortlessly, and I kinda like doing them, so I might easily come to think that anyone could. But that might be biased. It will but the reviewer wouldn't normally even know what the container is. So what was the scenario you imagined that this would come up in? I imagined a perhaps inexperienced CO asking the reviewer, typically a more experienced cacher, if their container of choice was fine, and getting an answer like "that container type has the following known issues: [...] so it might be a good idea to consider something else if those issues apply to your hiding place." I'm getting the idea that you think reviewers shouldn't be able to talk about this kind of thing at all, so I thought it relevant to point out that the example you chose is something reviewers were arguably meant to enforce at one point. E.g. that the "allowed topics" can change. Of course now that it's been agreed that PTs are ok, individual reviewers have to stick to that. If that's trivially possible, then I guess the location isn't completely blocked. I guess I'm assuming either the reviewer would notice that and not ask, or the CO would notice that and point it out in their response to the reviewer and that would be the end of it. I own a multi, the last time I found a multi was today. But my premise to this was "Ignoring remote locations for a while, is there any merit to this type of targeting of unpopular caches in otherwise busy caching areas?" And I said I have not decided what my own opinion on this is, but acknowledged that I'd play the devil's advocate if need be. So if you'd like to discuss this further, could you perhaps do it without making it be about me personally? I was taking "leaving almost no space for anyone else" to entail that there in fact is someone else. From this response, and your many others, I understand this generally doesn't seem to be the case in your area. So if these were the rules and I were a reviewer in your area, I probably wouldn't think they apply. (As a side note, that kind of location would have been great use of one of the new virtual caches.)
  18. Who do I contact and talk to if I have a problem with a reviewer? I am trying to hide and publish my first geocache but the volunteer reviewing my geocache asserts that it is in Indian Reservation Land despite the fact I have a vast amount of evidence to prove it is not. Please help.
  19. I've read a couple threads about Covid-19 and caching, and it got me to thinking: With all of this talk of social distancing and PPE, would there be a legitimate case for cachers to create virtual caches? What are your thoughts?
  20. A false-positive test will do that. It happens. They don't talk about it.
  21. What's dangerous for one child isn't necessarily dangerous for another child. Children learn from parents, peers, teachers, friends about what constitutes safe actions vs what constitutes unsafe actions and they learn those things at different ages. They don't learn it from osmosis, so your point about a child's age not mattering is also not a valid point. Let's use your railroad example. Let's say the child caching with you is 15. By this time, there's a strong likelihood that they realize trains will either severely injure you or kill you if you get too close to them due to their weight, being told by parents and peers, seeing movies/videos, etc... Now let's look at the 3 year old. Their exposure to trains is probably limited to Thomas the Train or The Little Engine That Could. They see familiar faces and trains that talk, are friendly, and are things that have feelings and the ability to do things that people do. They're not things to be cautious about because they haven't learned that yet. They see them as things that they can interact with. The "choo choo" is a friend, not a 300,000 pound engine that can't stop in time to avoid hitting, maiming, crushing, or killing a toddler that doesn't know any better. The same goes for caches near ponds, which was another point brought up. At some point, the dangers of drowning are learned by a child. Until that point is learned though, we do what we can to keep them safe. We have kiddie pools (where drowning can still occur) that are shallow and make sure to watch them. We provide PFDs. We teach them how to swim. There's no specific age for every child where they learn the potential hazards of water. So let's look at the 15 year old at a cache near a pond. They see water and they realize that it's something that has the potential to kill them but have learned how to swim, whether or not the body of water is safe to swim in, whether or not there could be potentially dangerous things in the pond (alligators, red tides, jellyfish) and what to look for to determine that, and various other things that they may have learned in order to keep themselves safe. A 3 year old sees a body of water and associates it with a kiddie pool, even though it may have current, is considerably deeper than the kiddie pool, and may have dangerous animals in or around it. They haven't learned all the coping mechanisms that the 15 year old has learned so they don't understand the inherent danger like the 15 year old does.
  22. A broken plastic container with a log so wet that it's unsignable, by a cache owner that 9 times out of 10 has left the game.. if that's vandalism, then I contend you just replied just to hear yourself talk. But with 10,000 more posts than me I should have expected that.
  23. You're clearly enthusiastic about geocaching and want to talk about it. That's a great thing. However, you're not an expert at this yet. While it's ok to share your opinions, I think some of your posts come across as the only way to do things, and not all of them have been what I would consider the preferred technique. I've been at this for over 13 years now and am closing in on 10,000 finds. I think it's fair to say we have a decent amount of experience at this point. But at the end of the day, I am just one geocacher, and I don't pretend to have all the answers. I try to share my experience, opinions, recommendations, or my personal approach as only that, and not as the "right answer." I don't always remember to do it that way, but that's how I try to approach things: rather than telling someone what to do, I post about what I have done, or what I have seen, or what I think, or what I'd recommend. All in all, this forum is pretty well behaved compared to some other corners of the internet. And if nothing else, we all have at least one thing in common: we are all interested in geocaching. So don't lose heart. But for now, perhaps consider sitting back and doing some more reading, to inform your opinions and experience some more, and asking questions instead of answering them.
  24. Avast! Got me event on the calendar and the port authorities notified to expect a band of hardies to drop anchor on the 19th of September. Anything going elsewhere?
  25. Everyone, Say what you need to say! Its 2:00!!
×
×
  • Create New...