Jump to content


+Premium Members
  • Posts

  • Joined

  • Last visited

Everything posted by Arrow42

  1. P3, 300mb ram, and Windows ME? Well, unfortunately, your going to have trouble all over the place.. websites are built and tested on computers with more resources... it's an unfortunate side effect of the "web 2.0" world. Both of those are insufficient for browsing modern websites and both have massive security flaws. IE6 (and I suppose IE5) both handle java-script poorly.
  2. Arrow42

    Please hold me

    Thank you, now I feel better able to face a brave new world.
  3. Arrow42

    Please hold me

    Something has changed from what I'm used to. That scares me. Please hold me.
  4. or observe $10,000 donations. Still insufficient data.
  5. Ras_oscar's post is an example of what I was saying before. (It is a good idea anyway)
  6. Oftentimes people have their own rules of fair conduct that have no grounding in official documents. Briansnat's list covers the official rules... anything beyond that is either socially accepted norms (unwritten rules) or individual opinion.
  7. Yes, I'm fairly sure that's fine. I've known others to do that.
  8. Since kayakanimal isn't using his charter membership, can I have it?
  9. Mine too. I was an administrator for a site running an instance of mediawiki. Mediawiki stores passwords in a very sophisticated salted hash.
  10. This isn't a little more of a deal as you make it out to be. Consider the simple "hacked database" event. Scenario one: Plaintext The vast majority of users use the same password everywhere. Now, the vast majority of user's on geocaching.com are compromised across multiple websites. Yes, it's silly to use the same password everywhere... yet, if you are a dev and you ignore that simple fact then you don't deserve the trust those people put in you. Scenario two: encrypted database Only mildly harder to break then plaintext.... especially since the hacker can now do so at their leisure on their own computer. Scenario three: Salted hash Each password is hashed separately. Unlike plaintext or a encrypted database, each password must be brute forced indivisibly. Each hash can take 40+ hours. While thats not a big deal if you only need to do it once, it starts to matter if you need to do it six million times. And the best thing... salted hashes are easy to understand and there are off-the-shelf/open source solutions that are relatively easy to implement into an existing security system.
  11. Very cache-dense area. It's a good thing on the one hand and a bad thing on the other. Either way, it is what it is.
  12. Opps, I posted this without reading your entire post! doh!
  13. A few things came to mind while scanning though previous posts... Listed in no particular order: Active cache owners who place tons of caches but never maintain any of them. Missing travel bugs (frequently exacerbated by an MIA CO) Pill bottle's used as caches... Like, seriously, put it at the bottom of a place that collects water, dufus. Worthless hints - "You'll know it when you see it!" - yeah, thanks alot. Micros where a 50 gallon oil drum could have been hidden with ease. Having a small cache go missing before the next person even looks for it. People who don't log DNFs or make up stupid conditions to justify not logging a DNF. "TFTC" - If you want to express thanks then at-least use whole words. If your not really thankful, then don't lie. Muggles who just won't go away! Really lady, you just HAD to sit there in your car in front of the cache for 30 min. Cache pages that show zero effort. Yeah, I realize my "Pet Pieves" may be entirely unreasonable/silly/futile. I don't take any of them that seriously... no lost sleep:).
  14. I didn't realize that GS was a public company that released financial data. Hay, "from thin air" is a reliable source.
  15. I have 6 caches hidden and I've helped out with 4 more. Most of the time the cache is approved within an hour, but I have seen them take up to 48 hours.
  16. there's no review process. Have you accepted the "Terms and Conditions"? Pay close attention to any messages the page gives you after you try to log a find... there might be a problem somewhere preventing you from logging a find. Not having ever accepted the ToC can do that.
  17. TheHunterSeeker, your comment strikes me as very rude. Motorcycle_Mama's comment was a polite rebuke.
  18. That only works in the rate instances where you item is found by a honest person. If that happens, then your cell phone number on the back would serve the same purpose and not cost you a membership fee. We put asset tags, and set the home screen of all of the blackberries we send out to include our 800 number in-case the device is found... it seems to work only about 20% of the time. We only have 4-5 lost per year however, so my sample size is fairly limited.
  19. Some cachers will leave a signed dollar bill in the cache for the first to find. I've seen $2 bills used as well.
  20. Default font size can be changed on the user's end. Press and hold CTRL and then tap the + key. The - key to make it smaller.
  21. On the inverse side of things... a "Unignore by user" would be nice as well.
  22. There is a particular cacher in my area who seems to never maintain their caches. He (or she, I guess) keeps placing new ones and occasionally finding them, but it's almost like a 50/50 shot if the cache is missing or in bad shape when I see his name on the GPS. So... I'd be tempted to use a feature like this. Even if I wasnt, it only adds a useful feature to the website with no downside.
  23. Here's my take on what to log and when to log it: If you like it, great. Feel free to discard it if it doens't suit you.
  24. I'm waiting for the "priceless" line.
  • Create New...