Jump to content

GeoJunkie

+Charter Members
  • Posts

    303
  • Joined

  • Last visited

Everything posted by GeoJunkie

  1. Additionally, it sets the NM attribute, which will exclude it from PQs, I believe.
  2. Does anyone know how to get hold of the developers? They log on nearly daily, but I've tried emailing them from the email address on their website and using the GC send email function, but have never received a reply. My stats aren't correct on the US State/US banner. Here's the banners I get, and my stats on cacherstats: Any ideas why my banners show a ranking in Nebraska and the world, but not the US? Either that or know how to get hold of the developers?
  3. I have one I recently placed on my front porch. Took some tweaking as I found out some unique challenges. For one, accurate coordinates are a must, plus put something there so people KNOW they're at the right house if you live in a dense area! I live in a duplex and my neighbors got to meet some wonderful area cachers when I first put mine out. now I have a stained glass Nebraskacher sign on my porch to guide people to the right house if the satellites get fuzzy. I'm OK with finding private property caches as long as the placer has identified how they are allowed to send me there. If they tell me it's their property, or their mom/brother/sister/etc who said it's OK, then I'll go. Sometimes I even get to meet some nice area cachers!
  4. Just an additional note. I was poking around the website, and they have a customer service number on the Terms and Conditions page (but not on the contact us page - go figure :? They're on Pacific time, so I'll wait until it's a decent time there and call them. I'm interested in finding out what they have to say...
  5. Checked my order status this morning, and it shows completed, but no more information: Interestingly enough, it shows completed on Mar 20 at 0248, which happens to be the exact time I ordered it, even though the last time I checked it on March 26th it was still pending. I've sent them the following email, we'll see what happens: One thing is for sure. They have to be losing business fast. I for one don't intend to make a repeat order and the only reason I haven't asked for a refund yet is because it may have actually shipped. If it doesn't resolve soon, I'll be looking for my money back.
  6. I had that with mine BEFORE upgrading to any Beta. Happened last week, and just installed my first Beta this morning. It seems there's been some shifts in waypoint rules that were causing issues on manually created waypoints. I backed up and cleared my database, then reloaded fresh from my pocket queries. Haven't had that problem since.
  7. Well, well, something new to jump in on! I wonder if we couldn't have the rating AND recommendation system, combined with tags (how's that for a combined solution!) Here's what I picture: Cacher A goes and finds a cache. He enters his log. If he posts a find or DNF, he's brought to the log completed page. We've all seen it. On this page, there is an option below where the individual CAN click on a 5-star rating system, if they so choose. There is also a checkmark to "Add this cache to my favorites list". Cacher A really enjoyed this cache. In fact, it was his favorite ever! 5 stars and added to the recommended list. Cacher B found a lame LPC right next to a stinky dumpster. When he logs, he selects 1 star. Cacher C found the same cache as Cacher A, but she's not really into that kind of cache. Not really a favorite, but it was decent, so she gives it 3 stars. Cacher D is getting ready to go caching. He runs a pocket query, filtering out anything below 3 stars. Why, because that's how he plays the game. He will visit the first cache but not the second. Cacher E knows that he likes the same caches as Cacher A, so he goes after that first cache because it's on his favorites list. Cacher F could care less about any of this, and will choose caches based on descriptions and logs. He doesn't believe in these rating systems, thank you very much. So, the ratings and favorites are ignored, and since they are not intrusive, it's easy to do. Cacher G looks at the small box on the page showing how many cachers marked this cache as a favorite, and picks one that gets last of recommendations. So, there you go - something for everyone. Something allowing ratings to be contributed, favorites to be listed, and the ability to filter on one, both, or neither, depending on personal preference, without pushing anyone to accept something they don't like. If you look at the oft-quoted Amazon model, it works pretty similar to this. With ratings, recommendations, and even logs to look at (aka reviews). People will shop Amazon based on their own preferences. To quote the too-often quoted: "Can't we all just get along?"
  8. Wow, great. I placed an order on the 20th and was just wondering why it hadn't shipped. Guess I need to settle in for a really long wait. Wonderful, now my disabled cache will be waiting even longer to come back up.
  9. Just found one in the middle of the woods. The hint was: "I wood hide it this way." Yea, OK. So it's in or near wood. Um..I'm in the WOODS! Yep, that sure narrowed it down!
  10. So, I'm browsing along on the GC site, and all of a sudden I get the page: It sure came all of a sudden, and I never noticed an announcement. Is this Groundspeak's new of of saying "site's broke"?
  11. Apparantly you can move it to an unknown location: http://www.geocaching.com/track/faq.aspx Yes, all you have to do is go to the TB page, and look at the pulldown just below the trackable item option on the right. If you own the bug or own the cache it is in, there will be an option to "Mark item missing". Once you do that, it will no longer show up on your cache page.
  12. If you like to read, I just started a book with an interesting twist on this thread's topic. It's called Abomination by Colleen Coble, where a killer leaves...parts...near a cache he hides.
  13. Well, here's some good news for a change! My Purple Bear TB, which I had posted an obituary for when it fell off the planet has come back! He had been dropped in a cache in August, 2007, discovered that December, then discovered later that month at a meet and greet. In September, someone posted that it had been left at the meet and greet and never turned up, so I marked it missing, posted an obituary and considered it gone. This week, a log popped up, turns out it was in the bottom of a swag bag! My bear is back from the dead!
  14. I think it's time to say farewell to A Little Screwy, my entrant in the Great TB Race. He didn't even make it off the starting line. It's still showing in the cache, but by the logs, I think someone removed it a couple weeks ago and just never logged it. And my friend who I'm competing with has hers pulling lots of points right off the bat! No fair!
  15. You can back date the log to the actual date you found it. Nothing dishonest there...you found it, just took a little longer to log it online!
  16. A string of "finds" after my honest DNF... November 2, 2008 by BooBear (456 found) Looked and looked all around. No luck finding it. November 2, 2008 by BooBear's honest friend (148 found) Some how this just seemed oddly off to us. No luck finding it... November 14, 2008 by What da huh? (1220 found) WE got this one-. Replace it.. The 'ol one cant be got-. Thanks ~ November 14, 2008 by Um..duh? (176 found) Help replace this one... Followed by a couple actual finds, then the topper today: January 22 by When in doubt, put your own out (3680 found) Well, got this one after a fashion. The cache I saw was stucin in an area that I could not get it out.. even after 2 trips back to the truck for supplies and tools. While trying to get the cache, I got it into a position that it dropped out of sight. So the only way to get to it would be to cut the tree down, not an option. After the 3rd trip to the truck, I replaced the stuck cache with a match holder I had with me, so the cache can still live on. To add to the fun of this hunt was the fact that I was doing it at 11 pm, in the cold and dark, and not trying to draw atttention to myself by drivers on the road. Thanks for the cache and the new story.
  17. I don't know if you noticed this...well, your story tugged at my strings enough I went to see the cache an TB to get to know Roy a little better. Did you happen to catch that he was spotted in a cache this October? Maybe you should contact the discoverer...Roy may be still out there!
  18. That one happens all the time, and sees pretty legit. At least he went out and found it again. A lot of people just back date their logs when they create an account, which still is reasonable, but he went one step beyond!
  19. OK. What exactly does this mean? They got it...but it can't be got....
  20. It appears they were working until sometime yesterday, now they are not going through.
  21. Put me on the list, too. I have my own domain with the mail hosted by Google. Had a recurring PQ that ran at 10/31/2008 12:55:20 AM that I received. Had four run since then. All ran successfully, but received all run today at 3:55:33 AM, 5:32:06 AM, 5:35:14 AM, and 5:36:45 AM. One is a weekly that always returns several caches. Previewed all and they have results. I'm with the others, there are no emails coming to multiple ISPs. I am receiving emails through other means at the same address, but nothing from GC. Sounds like there's a problem on their outgoing mail server...
  22. That's normal behavior for a daily query. If you insist on having one run every day, it is given the lowest possible priority, and it doesn't reenter the queue until 24 hours after the last run. I have one scheduled daily, too, but I accept that it won't necessarily run every day on particularly busy days. That's normal, but the behavior last week - running daily queries while leaving new ones alone - was bad. At this point, is there ANY chance of Groundspeak acknowledging there was a problem? Also, BTW, this did roughly concur with a system release. Could the two be connected?
  23. The only "Official Word" we got is that everything has been working fine, just slow. So there really was ever a problem... Hence the highly satisfied clients you see in this forum. BTW, my testing fits Nudecacher's. PQs created during the troubled timeframe never ran, but PQs created before and after work fine. I think the generator was actually down and/or severely bogging, and new PQs were being corrupted. Perhaps their related to the most recent release?
  24. Ditto here. Deleted and recreated a PQ and everything ran fine. Looks like they fixed whatever was happening, but you gotta recreate to kick it back in.
×
×
  • Create New...