Jump to content

HHD

+Premium Members
  • Posts

    219
  • Joined

  • Last visited

Everything posted by HHD

  1. Not really sure why this would be useful to anyone, but click on the Union Jack to see an English version. Union jack? That's English...I'm from America...duh...I speak American. You said if it was written in English, not if it was written in American. Come on guys, it's not too difficult, I've managed the process in reverse on these forums for a few years now. For a rough 'n' ready translating system from English to American just remove all extraneous letter Us and convert Ss to zeds then to zees. MrsB Ohhhhhhh, now that makes since. I'll have to try that.
  2. Ss far as I know there are only 2 ape caches left...one in Germany and one in Brazil. The location less caches have all been archived...and the chirp caches have a special beacon attribute. I believe they are all puzzle caches as well.
  3. Not really sure why this would be useful to anyone, but click on the Union Jack to see an English version. Union jack? That's English...I'm from America...duh...I speak American.
  4. I cache in Wisconsin...so not Canada bit close. I love caching in urban areas so I can still vs he in style, however when I'm out on the trails I have a great pair of keen waterproof boots. Stylish and comfortable.
  5. If it was written in English I might use it...but I am too lazy to try and figure out another language.
  6. Good luck. Hope to see you out on the trails someday.
  7. Any other ideas before I post on the website forum?
  8. (actually, it still is not editable, at least not by me) I don't know what's going on. I changed the settings so it would be editable by anyone. I googled it and it looked like lots of Google Docs users were having the same problem. I'll see if I can find another site to host the schedule. I wouldn't put too much effort into it if I were you. You can only stretch a joke so far before you break it. Wait...you mean you aren't supposed to beat a dead horse?
  9. Eventually the gc app will include chirp functions as it is on the ant+ open source network.
  10. I don't care about the quality of the hide. It could be a powertrail for all I care...just maintain it.
  11. I second the pn40. It has a bit of a learning curve but if you read the instructions...It's not so bad. Ps they are around 100 bucks on eBay.
  12. Thirst ftw is what I see. And ibln
  13. That is beautiful. Exactly the concept I had in mind. Thank you for your feedback.
  14. That's an awesome idea. I love it. Can you do some more pics of how you created that one?
  15. So to refocus this thread.... If you like my idea great, if you like the concept but don't think it will be approved how can we change it to get approved. If you don't like the idea that's fine to. But I'm really looking for ways to improve the concept before I post it in the correct forum, so if you hate the idea and have nothing to offer on how to improve the concept of limiting new hides of cos that are ignoring their maintenance duties then please feel free to post why you dislike the idea in a constructive way.
  16. The system works well as is. Why rescind people's privileges? Hey! Let's try working within the system! Wow! What an easy answer! I do want to work within the system and use the tools provided to come to a solution. That is why I would like gs to enforce the maintenance guidelines and I am trying to offer a way in which to do that. If it can be handled with out an additional step for reviewers I'm all ears.
  17. I think the issue here is a misunderstanding of the role of geocaching.com in cache listings. GC.com (aka Groundspeak) is a listing service, not a caching service. Groundspeak does not provide caches except in a very small number of instances. Attempting to eliminate caches and cache hiders based on quality or other metrics is not in Groundspeak's business model. They provide tools that can be used by cachers to evaluate the difficulty, terrain, condition and quality of the caches they list so that those cachers can decide for themselves whether they wish to seek the caches. If Groundspeak has good information that a particular listed cache has gone missing for a long period of time, they will de-list the cache based on unavailability. And Groundspeak will de-list a cache that is known to be in violation of the law. But they have never, and likely will never, de-list an available cache because of maintenance issues. And they never will prohibit a cacher from listing caches based on length of caching experience or maintenance issues with other caches. It's the same reason virtual caches were stopped; Groundspeak does not want to be involved in decisions about quality. It's not that Groundspeak doesn't care; it's just that what you are asking is completely outside the model of how the listing service works. Your campaign to have Groundspeak take official action of some kind is not going to succeed. My advice is this: if you don't like caches that have ongoing maintenance issues, then don't search for them. Thank you for your input. Those are some new objections I haven't encountered yet. Forgive me for being a bit of a noob and not knowing how to link to the knowledge books but if I understand the concept of Groundspeak and geocaching.com they are a listing service that houses a list of approved caches. If I'm understanding your argument correctly your point is that they are simply a listing service not a policing service. I agree that they normally leave it to the reviewers to be the police rather than deal with it on a corporate level but by definition aren't reviewers representatives of the company? They are charged with maintaining the standards of placing hides and when a violation occurres they are the ones who take action. If you read the knowledge books about cache maintenance it does clearly state cos are responsible for regular visits to fix issues that happen over time. So is it not a violation of that policy to ignore maintenance issues? And if it is can't we slow the proliferation of these cos caches until they fix the problems they already have? I'm not saying they can't ever place hides. I'm just saying if you have 5 nm caches..at least fix one before you hide more.
  18. Yes! Let's make geocaching what YOU want it to be! That's a pretty good definition of 'cache police'. You might try getting off your highheeled horse, and let people enjoy what they enjoy doing. Next on your agendum? Caches ALL IN CAPS? Caches with mispeelings? The system seesms to work fairly well as it is. There have been many arguments why it is not a good idea. But you blow those off. Only what you want is important? Yup. Cache police at work. As far as what I want, I think we all want the same thing. Caches that don't have soaked logs for months on end with no co intervention, no broken containers or missing containers that are being ignored by the co. Most cos tend to their caches in a resonable amount of time. However there are some cos that ignore maintenance because it isn't any fun and they just keep putting out new caches while ignoring the multitude of nm logs piling up. I hope to find some way to bring these cos to light and have them start maintaining their hides like the rest of us do before they put out any new hides. I fully admit this may be an up hill battle. It is just a concept. I am using the forums to bring out the thoughts of other cachers much more experienced then I. I may gloss over some of the negatives because I'm looking for ways to improve the idea not shoot it into a bloody pulp, stamp it out and in general hate on it. That makes me one sighted I fully admit. Like I said I'm trying to find s way to improve the game for everyone. Personal attacks on me are a given. So I will ignore those. As far as the system working well enough now....really? If it was working why are the majority agreeing it is a good concept even of it might not fly?
  19. I completely agree about the nm and na logs people are not willing to use. If you use na and nm more then annually you are deemed cache police. if you don't use them you are just ignoring the problem. I learned long ago that letting a problem fester only makes the problem worse. The same is true in caching. If you don't use the tools given to you the cache and the community suffers. When I use nm logs I hope to bring co attention to a problem. If that doesn't work or the cache has multiple nm logs or it has been months since the log and no attention paid by the co then I use the na. I also use dnf and note...I use most of the log types. If that makes me cache police then so be it. I enjoy this game and want others to have a good experience to. And thank you sol for the compliment. I truly want opinions. The more the merrier. Together we can find a way to make this idea work.
  20. I used my phone for over a year until I bit the bullet just recently and bought a Gpsr. I always carried around a portable battery pack (about 35 bucks at Walmart) that plus my phone battery gave me about 5 hours of caching.
  21. Lots of people do that. It's really up to you. But don't forget...it is about the fun not the win.
  22. I'm not encouraging owners to clear nm logs without doing the maintenance. I'm merely saying I'd be dumb to think it wouldn't happen. What my proposal does do is put another layer of cache protection in place so that we don't let nm logs go on for years with no action while the cos go out and hide new caches weekly.
  23. Interesting concept, but it won't work. If you implement this, a lot of cache owners will finally figure out how to use the Owner Maintenance log to clear the NM flag. But those owners weren't really the problem, most of them fixed their cache and just didn't know how to clear the NM attribute. The problem is that the truly lazy cache owners aren't going to suddenly go out and maintain their caches. They'll just clear the attribute and leave the mess out in the field. This will happen I'm sure but eventually they will be called out on the carpet about it. You can only cheat the system so many times before the community will call shananagings.
  24. Thank you for you support and great points.
  25. And which cache are you referring to? The original, which is still there, but hard to find, the first throw-down cache, or the second throw-down cache? (Yes, this actually happened.) And then there's the follow-up issue when that happens - the owner checks his cache, and sees that a lot of people have logged it on line, but don't have a signature in the cache log (because they signed cache #2 or #3). So he starts deleting logs, with the inevitable blow-back. And that's what happens when people replace caches they don't own. Which is highly unlikely to happen if the cache owner has already asked people to replace it if needed. The problems associated with throwdown caches occur when it is done without the approval of the cache owner. The problem I see is that when you have a proliferation of gcrm caches in an area and your caches are close by people tend to assume this is how all caches are in the area. Then a non gcrm cache that has a unique hide or is maybe more challenging gets a throw down. So now you have to say your hide isn't gcrm because others around it are. And not enough people read listings before they throw down.
×
×
  • Create New...