Jump to content

Bunya

+Premium Members
  • Posts

    503
  • Joined

  • Last visited

Everything posted by Bunya

  1. I may have missed mention of it in postings above, but I think the most common risk in geocaching arises from the fact that (particularly if you are alone) you can easily walk into trouble of some sort because you are looking at your GPSr and not where you are going! I believe at least one geocaching death has been attributed to this as a cause. I know that I’ve nearly broken my ankle (in a rabbit hole), walked into quite a few branches thick enough to make me regret it and slipped on a scree slope that had been firm ground just before I looked at my GPSr. I usually try to check the surroundings and/or stop each time I look at my GPSr, but it’s a precaution easily forgotten in the excitement of the hunt.
  2. But didn’t you know? Some time ago (your choice of) God decided that mankind had made such a mess of the world that we should be wiped out. However He/She/It decided first to get together a representative of all non-human living creatures and put to them the following proposition. Unless two of them speak up in favour of mankind, we will be eliminated. The only one to support our survival is the domesticated dog. God is about to wipe out to humanity, when the mosquito says “OK, perhaps they are worth keeping.” That’s why we are still here.
  3. If you don't like them, you can go to Groundspeak Forums > Your control panel > Forums > Board Preferences and choose to suppress members' signatures (and avatars).
  4. I think your belief that LPCs are known worldwide is a bit misplaced. In Australia they (the skirts) are not widely used. I wasn't sure what one was until I found this picture:
  5. There are at least two ways other geocachers could have known you did this and YOU wouldn't know that they know! They could either have that archived cache on a private Bookmark list or they could have a notification for found logs covering the area of the archived cache. The geo-police are always watching. . .
  6. Anyone else noticed that the picture in the souvenir for 6th August is "impossible"? The rightmost star would be hidden by the moon.
  7. Thanks for that information. I think it's because I usually put a watch on or bookmark caches before I find them that I hadn't noticed the change. I just happened to do a few recently where I hadn't done that. I agree with you about liking to see my logs after I've submitted them in case I've made a serious error.
  8. I'm not sure if this is a bug, or whether notifications are supposed to work this way (ignoring your finds). I have a notification set up for all log types on traditionals covering my area. It seems to work fine except that I don't get notifications of my own finds - I do get them if others find caches. Is this a bug?
  9. Actually, only in American English: elsewhere it's "neighbour".
  10. It's 4000 characters. I have known people to write logs so long they've filled up the log and continued it in a second log, a note. Thanks for that. I assumed that would be the way around the limit, too!
  11. Not entirely OT, but I can't see the answer above or in the "Help Center". I recently got an email from a cacher who had found one of my caches saying he had tried to log a find but it was rejected as "Max Length Reached". He put his log in the email and logged a shorter version on the cache page. What is the "Max Length" for a log?
  12. You do lose the smiley face on the map, but not the find. I assume you mean this cache: Two Towns
  13. I'd never tried creating a steganography puzzle and my first go has struck a problem. I tried using mozaiq, but the hidden information seems to get "lost" when I upload the picture to a cache page. Can anyone help with this or point me to another method where this won't happen?
  14. Since we’ve had the two millionth active cache now published, and I saw it quoted that over three million had been published, I wondered what proportion of my found caches (caches found by me) were now archived. To my surprise I found it was currently exactly one sixth. I wondered how this compared with other finders. Is your “now archived finds” ratio near this number of about 17% or is there a widely varying range?
  15. Sorry to go totally OT, but every time I see the <3 emoticon I can't help thinking of the "Zits" cartoon with the caption: "<3 sara. What is that emoticon supposed to be? It's a heart. Ohhhhh … Now I see it! I thought I was being mooned by an angle bracket." Is the "sounds like" connection between your caching name "Skitz" and "Zits" pure coincidence?
  16. I think the answer is often "No, they don't read the cache page - at least not anything but the cache type, coords and hint". More than once I've had cachers complain that one of my caches should have had a hint. In fact it did have a hint, but it was in the description, not in the “Additional Hints” area. After all, this area is called Additional Hints, implying that there may be hints elsewhere!
  17. Sorry to persist with being OT, but my point about "Crumbs!" is that it is a euphemism for "Christ!", but few would realise this. I was trying to show how silly this OT discussion had become. My point was clearly not well put.
  18. So you would object if I used "Crumbs!" as an expression of surprise? I wonder how many people realise that it is profanity too.
  19. I don't get your point - of course I know slashes are characters. The dd/MMM/yyyy is an allowed date format under "account preferences" - and the one I prefer. I've used it for years without problems. But having changed from IE9 to IE10 I was blocked when I tried to edit the date on a cache page I had started setting up under IE9. So I think it's a geocaching.com bug.
  20. I just changed from IE9 to IE10 under Windows7. Now when I try to edit the date (in the format dd/MMM/yyyy) on a page for a cache I started setting up under IE9 I get the error message "You must enter text with 10 or fewer characters". Anyone else got this problem? Added in edit: I found a "work round" by using the numeric date format dd/MM/yyyy (which was accepted under IE10), but there is clearly a bug here.
  21. Of course PM geocachers can “watch” caches in other ways. By way of bookmarks or notifications, for instance. So you don’t even know how many “watchers” there really are . . .
  22. I think they're using it as a variant of rip-off. rip off vb 1. (tr) to tear violently or roughly (from) 2. (adverb) Slang to steal from or cheat (someone) n rip-off 1. Slang an article or articles stolen 2. Slang a grossly overpriced article 3. Slang the act of stealing or cheating The standard slang in geocaching has always been cache maggot to describe a member who routinely steals geocaches. I think we should just stick with that term. Thanks for that explanation. I agree that the term "cache maggot" fits perfectly!
  23. A bit OT, but can someone please explain the use of the word “ripper” in this context? The standard (dictionary) meanings I can find for “ripper” are either “a tool that is used to tear or break something” or “a murderer who mutilates victims' bodies.” Here where I live (Australia) it is also used as a slang term for “an excellent person or thing”, for example “It was a ripper party!”. However in this thread it seems to be used as a synonym for “thief”. Where is this usage from?
  24. Oh dear, not that old bit of nonsense. No educated person at the time of Columbus, and certainly few sailors, thought the Earth was flat. However, Columbus did think the round Earth was smaller than it was, and always thought he was exploring the east coast of Asia, not a new land. He also never set foot on the mainland of what is now called North America. And no, this is not an April fool remark as it’s the second of April here in Australia as I write this. Normal transmission may now resume.
  25. Time to make the FTF game legit? According to Wikipedia, “Legit” is an “American comedy television series”. I see that the OP is in Canada, not the US, but I assume that makes it clear that your suggestion is a joke!
×
×
  • Create New...