Jump to content

GEO-BUM

+Premium Members
  • Posts

    17
  • Joined

  • Last visited

Posts posted by GEO-BUM

  1. Finally I got the Android browser working again. Thanks to all who tried to help with my problem.

    This is what I did......

    Went to home page..then to applications..next to settings..then to applications..next to manage applications..then hit all..next hit browser then hit clear data.

    Now I tried to sign into geocaching.com again from the Android default browser and presto..it works. AMAZING!!

  2. On my phone the first letter is automatically capitalised. Since my password isn't I have to select lowercase. Maybe that's the problem.

    It maybe an issue because every time I log in with geo-bum it goes right back to Geo-Bum. Can't make it quick. What I didn't know was signing in was case sensitive. I think that is what you are saying. Anyways I switched to Opera Mobile browser and I can log in just fine now. Not sure why but I'm happy I can.

  3. I had this same issue with the default browser. It isn't very fine tuned for any forums at all. I solved the issue by using Chrome over the default... I also tired firefox with no luck.

    Thanks for the info. I am using a Samsung Stratosphere and when I checked on loading Chrome into my cell it said...my cell isn't compatible with this version. Just not my day I guess.

    Chrome only works on ICS (Android 4.0) and newer, and requires certain hardware capabilities as well. You're probably running Gingerbread (2.3). Have you tried Opera Mobile, or Dolphin Browser?

    Wow!!! I put Opera Mobile in my phone and it worked..... Yahoo!!! Go figure???? Thank You...Thank You!!! I will keep you informed as to how it continues to work. For now I have piece at last...lol.

  4. That is problematic to other cachers that may want to place caches in the same area or to the cacher themself by waiting too long and then the immediate area gets populated by another cache.

    IMO, Bad idea all around.

     

    No not at all. When you place a cache and do the cache page but uncheck the ready to publish box, your hide location is yours no matter how long you wait to have it published. So there is no difference.

  5. OK then. You should not submit them until they are all hidden then.

     

    In my case I don't. What I do is hide them all first. Then type up all the pages and send them...but I uncheck the ready to publish box. Then I recheck all the cache pages to make sure all is ok. Next I check the box to have them published. After that I loose control and that's what I don't want.

  6. I have the flexibility to have them published in the order I want them to.

    It's my understanding that the reviewers already review and publish the caches in the order of their GC #. So if you want them published in a certain order, just submit them in that order. As long as you don't have issues with any of them you should get your wish.

    To be more precise....I should have said....with respect to location, since I hide in muti locations. Sometimes I don't know which ones I want published until they are all hidden and sent in for review.

  7. So is what you are saying is, you submit a cache or many caches and then the reviewer approves them but they are on hold until you click a button that 'releases' them?

     

    I see no problem with that idea. Sounds good to me.

     

    Thats how i am understand of what the OP is talking about.

     

    I see no problem with that as long as the submitter isn't allowed to hold on to publishing them for an extended period of time.

     

    I like that idea.

     

    As it is now...the submitter can submit and pretty much wait as long as he wants until having them published. But why would they wait to long anyways?? Isn't the reason you hide to have them published??

  8. Can you expound on the whys? What is the advantage?

     

    OK...first off it would only be an option. If you chose not to do it yourself leave it as it is. If you chose to do it yourself then you could. Now why??? First off it's the "FTF" issue (may not be important to most). I could have the caches published at different times through out the day (or night) when I want to, with out having to impose on the reviewers. They have enough to do. Second....when I have a bunch of new caches hidden (let's say 10 to 20) I have the flexibility to have them published in the order I want them to. Again not imposing on the reviewers. Remember....this would only be an option. It would not effect you if you didn't want it.

  9. I can see where this could be a good thing ,and a bad thing

     

    Publishing a cache just as your local ftf hound is starting work,

     

    Then another just as he goes to bed for the night etc etc etc

     

    Best left as it is I think, reviewers are pretty accomadating when requested to publish at specific times for events etc

     

    Yes you are right, they are accommodating for sure, but this way it's one less thing to take up there time. They are busy enough with checking out and approving cache hides. Having to be around to publish a new hide at a special request.....well one less thing they would have to do.

  10. I don't see how it generally matters when the cache is published. On the rare occasion that it does matter, a note to the reviewer should do the trick. Are reviewers overwhelmed with such requests?

     

    edit redundant word

     

    In our area there are a lot of new hides popping up all the time. For me having the control of when I want my hide to publish would be great. Most request are done well with the reviewers but asking them to publish a cache late at night, early in the morning or on a holiday isn't fair to them.

  11. I posted the below in the feedback. What are your thoughts???

    If you like it please go to feedback (link below) and vote your opinion.

     

    http://gsfn.us/t/19ivp

     

    Being an avid cache hider, I would like to see the ability of a cache owner to publish his/her hides when they want to. Why can't there be an option, where as the reviewer places the new cache hides in a queue when they have been approved? Then having a feature letting the cache owner publish their hides when they want.

    Why?? It would give the cache owner more control of the publishing of their hides and would take a load off the reviewer with all the special publishing requests.

×
×
  • Create New...