Jump to content

scooterj

Members
  • Posts

    94
  • Joined

  • Last visited

    Never

Everything posted by scooterj

  1. quote:Originally posted by scooterj:I have just learned how widespread the destruction of all of my cache pages is. Take a look at THIS one: http://www.geocaching.com/seek/cache_details.aspx?ID=25122 Well, I have managed to get the images back by discovering that if you put BORDER=0 before the SRC= portion of the IMG tag, it wipes out the entire tag.... while if you put it after it works fine. Unfortunately I missed one IMG tag when making this edit, and the process of re-editing wiped it out of the original code entirely. So I have no idea now what the URL was of the image that got destroyed. Seems like a pretty crappy filter system if the order of parameters can cause so much damage. The cache still doesn't work the way it once did, though, thanks to the unwarranted and unannounced destruction of my validation system.
  2. quote:Originally posted by Doc-Dean:"Feature" right...... Free your mind and the rest will follow http://img.Groundspeak.com/user/30296_400.gif Yeah, just like every other sudden unannounced change as of late that breaks caches is a "feature". I have a traveller, and so far it hasn't moved far enough to be affected by this new "feature".But it has moved several states at a time before. The last time I needed to change a cache it took 2 weeks to get a response from an admin through official channels, though I did get a response in 3 days through the forums. In either case, that's far too long a delay for a cache on the move. Normally I have the coordinates updated within minutes.
  3. Oh it just keeps getting BETTER. I have just learned how widespread the destruction of all of my cache pages is. Take a look at THIS one: Union Cemetary This cache is entirely useless now. The broken image boxes were once photos of what you had to find in order to answer questions. (These pictures ARE hosted on geocaching.com, BTW.) And after each one there used to be a text box where you entered the answer to the question and a validator on my server would tell you if you were right and give you your certificate. This is one of a few caches I have that works this way. When some of these caches were approved, I was commended by the approvers for having a good system of validation and the people who have found these are all broken. Now, all but one of my Virtuals are ENTIRELY INOPERABLE and every single one of my physical caches is missing the pictures and diagrams that go with them. WHAT THE HELL is with this mentality of making sweeping sudden changes that screw nearly everyone over and ruin years of hard work on our caches, with absolutely no warning, no acknowledgement, and no plan for transitioning all pre-existing work to adapt to the new system? Then, just sitting back and doing nothing about it, refusing to recognize that this has been a terrible idea and that things should be returned to the way they were. This is NOT a way to run a business. Please excuse any typos, I am livid as I type. I did not spend the last 2 years setting up 28 of what I consider to be very nice caches if they are going to continually be broken by sudden, unannounced, arbitrary fits of administrative paranoia. Absolutely ridiculous.
  4. After reading all the pages of this thread I am lost. Is this something Jeremy is still fixing, is this something we all need to change at our own end, or is it broken forever? None of the IMG tags are working on any of my caches (when viewing the source the SRC= portion is missing, even though it shows up when I edit the listing) and none of my font colors work either.
  5. Just bumping this to hopefully catch an admin's attention since my email has gone unanswered so far.
  6. quote:Originally posted by worldtraveler:It would seem an easy solution now would be to get the TB graveyard owner to change the cache type to virtual. Well, that would be me. Unfortunately, I have tried that already... and the option to change it to anything other than Locationless is grayed out so I cannot change it. I emailed the admins earlier today so hopefully someone can figure out a solution and let me know what I need to do to get it working again.
  7. quote:Originally posted by bcj19:Ok, not to get too graphic here, but how did he get through the bone? I'm hoping the bone was broken into two (or more) pieces and that he didn't have to saw through it... Happy Hunting! _~ bcj19_ The articles I read sounded like he did it at the elbow. Then he wouldn't have to go through bone at all. Still I can't imagine having the willpower to do that with a pocketknife, it must have taken a long time.
  8. I'd just like to publicly thank dustyjacket, whose visit to one of my caches led to the discovery of an unattended campfire and a tremendous amount of trash. He spent time taking care of both of these situations before begining the hunt and then even tracked down a sherrif patrol vehicle to report the fire so that it could be checked on to make certain it was out. Good job! You can read dustyjacket's log here: Blue and Gray v2
  9. quote:Originally posted by Caching In:Scooterj: quote: I asked this team to change their log to a not-found, they said they don't do not-founds. That is like a field goal kicker demanding his 3 points, even when he's wide right! You can't just arbitrarily change the rules--deleted 'em. In my case the people redeemed themselves and changed their log entry. Hooray!
  10. I'm currently dealing with a newbie caching team who attempted a cache of mine with a 4.5 difficulty, failed to find it, posted a log accusing me of poor maintenance, and posted it as a find anyway calling it a virtual. I went out and found the cache to be perfectly in order. I asked this team to change their log to a not-found, they said they don't do not-founds. I replied back that I cannot let them keep their find because it cheapens the finds of those who actually completed the task. I'm giving them until morning to do so or I'm deleting their find.
  11. I've got a few that I have labeled as accessible. I struggled in deciding on each one because there is no fine dividing line that determines whether a person is disabled... nor is everyone with a disability disabled in the same way. The criteria that I use is that any person who is able to get around on their own with little to no assistance should be able to get to the site, and retrieving the container (or finding the plaque or whatever if it's a virtual) should require no more effort than a person might typically endure retrieving or observing a misplaced item within their own home. While I use the ClayJar system to rate my caches, I have a slight personal modification that I use. My personal modification is that I feel that anything with a rating below 2 on terrain or difficulty should be reachable by anyone who is capable of getting around on their own. If anything about the cache would make it difficult for someone with a disability to get it, I start the rating at 2. So, if one of my caches is rated 1 on terrain and 3 on difficulty, then it can be assumed that a disabled person will be able to reach the cache site but may require assistance from another individual to actually recover the cache. If I rate the terrain 1.5 then it means that most disabled people should still be able to get there but that it may be a bit more of a challenge.
  12. quote:Originally posted by scubagecko:Do most travel bugs vanish like this? So far I haven't decided whether to get one or not because I figure some bozo will take it and do nothing with it. Weell, here's my experience. I bought 8 tags. So far I have released 6 bugs. Here's the breakdown: - One was lost in a looted cache. Now in the graveyard. - One was taken by someone who let a grandkid take care of it and now it's in the graveyard. - One was taken by someone who thought the tag alone was the bug so detached it from the item and left the item behind, then never did anything with the tag. Now in the graveyard. - One was held for 3 months by the same person and finally put in a new cache a few weeks ago, only to then be reported missing by the next finder of that cache. Probably soon to go to the graveyard. My remaining two launched bugs are still sitting in a pair of caches I placed back in June that have not been found yet. Those could be safe there for quite a while... they are in a location that is reached by an unmaintained trail with sections of 10-feet-high overgrowth and three pairs of 300-foot up/down elevation changes. I'll still launch my last two bugs sometime, it's fun. My four vanished bugs all managed to get around quite a bit before they disappeared.
  13. quote:Originally posted by Rubbertoe:It is kinda funny - I grabbed http://www.geocaching.com/track/track_detail.asp?ID=7451 and took him on a journey - then placed him in a cache about 25 miles from his starting point. Wouldn't you know that the very next person to grab Dan ended up taking him straight back to where he started. Why? Don't ask me... heh That's what happened to me (except mine was on a larger scale) with a bug I eventually had to put in the graveyard. It was in a cache in Wisconsin when I gave it a new mission to get to a specific cache in Missouri. The bug worked its way south and finally ended up in a cache less than 2 miles from its destination. The person who placed it there, an expert cacher, added a note to the bug explaining that the bug should be taken only by someone heading to that particular cache and that once the bug reaches that cache it should not be removed. So what happens? Someone on vacation grabs the bug, doesn't read the note, and takes it all the way back to Wisconsin and puts it in a cache there... only discovering the mistake when he went online to log the transaction. (The bug eventually disappeared while in this person's possession... grrrr.)
  14. The trick to ebay is that every time someone bids the price goes up, and for a popular item anyone who bids early on is almost certain to be outbid. So, what you have to do is restrain yourself from bidding until the final seconds. When the auction is down to about the last 2 minutes bring up two browser windows. In one, log in and go through the bid process, entering the maximum amount you are willing to pay, and go all the way to the final confirmation screen but do not confirm yet. In the other window bring up the item's auction page and hit reload every few seconds, watching the time remaining tick away. Do not confirm your bid in the first window until the time remaining in the second window is less than 30 seconds. The closer to zero seconds you hit that confirmation button the better, just keep in mind that when you click the button a few seconds will elapse so don't do it too late. One of two things will happen. Either you will win the item because you got the last bid in, or you'll be outbid because someone either sneaked in just past you or placed an earlier bid for a higher amount. Either way you win, because if you don't get the item you at least get the satisfaction of knowing that whoever beat you is stuck paying more than you know the item is worth.
  15. The trick to ebay is that every time someone bids the price goes up, and for a popular item anyone who bids early on is almost certain to be outbid. So, what you have to do is restrain yourself from bidding until the final seconds. When the auction is down to about the last 2 minutes bring up two browser windows. In one, log in and go through the bid process, entering the maximum amount you are willing to pay, and go all the way to the final confirmation screen but do not confirm yet. In the other window bring up the item's auction page and hit reload every few seconds, watching the time remaining tick away. Do not confirm your bid in the first window until the time remaining in the second window is less than 30 seconds. The closer to zero seconds you hit that confirmation button the better, just keep in mind that when you click the button a few seconds will elapse so don't do it too late. One of two things will happen. Either you will win the item because you got the last bid in, or you'll be outbid because someone either sneaked in just past you or placed an earlier bid for a higher amount. Either way you win, because if you don't get the item you at least get the satisfaction of knowing that whoever beat you is stuck paying more than you know the item is worth.
  16. quote:Originally posted by ifranz:I think that the difficulty rating needs more definition. According to clayjar’s scale I think it qualifies as a 5 b/c the cache is “A serious mental or physical challenge.” and “ Requires specialized knowledge, skills, or equipment to find cache.” You’d kill yourself trying to find this one without the skills and equipment to climb there. As for the mental challenge, add 1000 feet of exposure to the most simple climb and it becomes mental challenging very quickly. Yeah, but it's only the terrain that requires the specialized skill and equipment. In order for the difficulty to be a 5, one would have to have special skills or equipment to actually find it after arriving at the cache site. The terrain rating rates what it takes to get there, the difficulty rating rates what it takes to find it once you get there. This sounds like a cut-and-dry 1/5 cache to me.
  17. quote:Originally posted by ifranz:I think that the difficulty rating needs more definition. According to clayjar’s scale I think it qualifies as a 5 b/c the cache is “A serious mental or physical challenge.” and “ Requires specialized knowledge, skills, or equipment to find cache.” You’d kill yourself trying to find this one without the skills and equipment to climb there. As for the mental challenge, add 1000 feet of exposure to the most simple climb and it becomes mental challenging very quickly. Yeah, but it's only the terrain that requires the specialized skill and equipment. In order for the difficulty to be a 5, one would have to have special skills or equipment to actually find it after arriving at the cache site. The terrain rating rates what it takes to get there, the difficulty rating rates what it takes to find it once you get there. This sounds like a cut-and-dry 1/5 cache to me.
  18. I just realized that I haven't received my weekly new cache notification email for the past ccouple of weeks, even though several new caches have been placed in my area.
  19. quote:Originally posted by dteec: Scooterj, How are you capturing your "official" logs? dteec - a curious web developer I've written a really nasty Perl program that I run after I finish a cache hunt and have finished logging all my finds. It makes an HTTP connection to my "My Cache Page" and scans the page for log entries that haven't been previously logged on my system. It then makes HTTP connections to those particular cache pages and sifts through to grab info about the cache and my log entry. Lastly, it checks my travel bugs and the travel bugs I have found to see if any of them have moved. If so, it grabs the new info. Grabbing the log info takes seconds since it only grabs my new entries. Generating the maps, though, that can run anywhere from 5 minutes to half an hour depending on how many new maps are needed and how busy the map server is.
  20. quote:Originally posted by dteec: Scooterj, How are you capturing your "official" logs? dteec - a curious web developer I've written a really nasty Perl program that I run after I finish a cache hunt and have finished logging all my finds. It makes an HTTP connection to my "My Cache Page" and scans the page for log entries that haven't been previously logged on my system. It then makes HTTP connections to those particular cache pages and sifts through to grab info about the cache and my log entry. Lastly, it checks my travel bugs and the travel bugs I have found to see if any of them have moved. If so, it grabs the new info. Grabbing the log info takes seconds since it only grabs my new entries. Generating the maps, though, that can run anywhere from 5 minutes to half an hour depending on how many new maps are needed and how busy the map server is.
  21. A few years ago before geocaching came about I saw a plane crash while I was golfing. I heard a plane sputtering and looked up just in time to see a low-flying plane suddenly veer to the left, hit the ground, roll a few hundred yards to a stop when it hit some trees, and burst into flames. It was very surreal, and the sounds it made were quite different than you'd expect from movies. The crash occured maybe 1500-2000 feet from where we were standing. We called 911 on our cellphone (they had probably already beeen notified but it made us feel less helpless) and rescue crews were there almost immediately, but everyone on board (6 people) died.
  22. A few years ago before geocaching came about I saw a plane crash while I was golfing. I heard a plane sputtering and looked up just in time to see a low-flying plane suddenly veer to the left, hit the ground, roll a few hundred yards to a stop when it hit some trees, and burst into flames. It was very surreal, and the sounds it made were quite different than you'd expect from movies. The crash occured maybe 1500-2000 feet from where we were standing. We called 911 on our cellphone (they had probably already beeen notified but it made us feel less helpless) and rescue crews were there almost immediately, but everyone on board (6 people) died.
  23. quote:I also utilize this to update my personal webpages, where I detail more information than I usually put on the cache page - including the possibility of spoilers, so lurk carefully. That's pretty similar to what I did with my site. (Warning, mine also has possible spoilers in some entries.) I have mine set up to automatically capture my "official" logs, I then go through later and add additional info for many of the cache hunts.
  24. quote:I also utilize this to update my personal webpages, where I detail more information than I usually put on the cache page - including the possibility of spoilers, so lurk carefully. That's pretty similar to what I did with my site. (Warning, mine also has possible spoilers in some entries.) I have mine set up to automatically capture my "official" logs, I then go through later and add additional info for many of the cache hunts.
  25. I was doing the same thing but I didn't get the impression that hey droppeed in that cache... since all that remains of that cache is springs and bits of burnt broken glass. But, it's possible. The real question though is why, if the cache was reported on March 9 as having been destroyed by fire, has every visitor since then logged it as a find while in the logs some wonder why no one has archived this cache yet?
×
×
  • Create New...