Jump to content

Zop

+Premium Members
 View Profile  See their activity

  • Posts

    606

  • Joined

  • Last visited

 Content Type 

Posts posted by Zop

    Update: Release Notes 1/12/10

    in Website

    Posted

    The new look has grown on me - I am now on the I like it side. Good work in hammering it out guys and gals in the development team!

     

    Not me.. There is still way too much whitespace but that's probably because of the issue with the "Visit Log" column causing all the rows to double in size.

    Also, why should we have to scroll way down to the bottom of the screen to see the rightmost column?

    Update: Release Notes 1/12/10

    in Website

    Posted

    Is there an ETA as to when Firefox and IEv8 will be supported again?

     

    I'm getting pretty tired of seeing this: gsbug.jpg

     

    Note the problem with the "Visit Log" column and the location and fixed width of the right column.

     

    I get this in both IEv8 and the latest Firefox on both XP and Windows 7 Professional. Screen resolution 1600x1200 on 20"FP

    Protest

    in Website

    Posted

    You complain that they did not do enough testing. Do you expect them to setup a sandbox environment, replicate the whole database and pay someone to look at every single cache every time they make any visual change? That is going a little far.

     

    Check every single cache page? Absolutely not. However HELL YES I would expect them to set up a 'sandbox' environment to insure the absolute minimum of disruption prior to pushing such a major change to a production environment. That's just simple IT basics. I would also expect a public announcement AT LEAST a full week prior to such a push as well as a heads up as to what to expect in visual and functional changes.

    Protest

    in Website

    Posted

    To protest the recent changes made to geocaching.com, we are temporarily disabling all our active cache hides (163 total) for one week beginning 01-18-10. If you are unhappy with the changes made to geocaching.com and want your voices heard, disable your cache hides along with us. Together we can perhaps get the point across.

     

    A&H,

     

    While I commend your effort to bring the issue to GS, I hardly think that disabling or even archiving your placed caches are going to do anything short of punish those of us who seek your hides.

     

    Rather than disable you hides, why not simply add a short note to the description or a log that

    "The above (or below) corruption in HTML you see is due to Groundspeak's incompetence and failure to thoroughly test the recent site updates/changes/downgrades and is not a reflection on the abilities of the owner of this cache. To help us resolve these issues, please contact Groundspeak (insert Groundspeak's phone number, complaint number etc... here)"

     

    Maybe if their phones start to ring off the hook and their email boxes begin to fill, they may get the point. Disabling your caches is not something that they will see let alone make any sort of impact.

     

    BTW.. http://www.Groundspeak.com/contact.aspx

    Protest

    in Website

    Posted

    To protest the recent changes made to geocaching.com, we are temporarily disabling all our active cache hides (163 total) for one week beginning 01-18-10. If you are unhappy with the changes made to geocaching.com and want your voices heard, disable your cache hides along with us. Together we can perhaps get the point across.

     

    A&H,

     

    While I commend your effort to bring the issue to GS, I hardly think that disabling or even archiving your placed caches are going to do anything short of punish those of us who seek your hides.

     

    Rather than disable you hides, why not simply add a short note to the description or a log that

    "The above (or below) corruption in HTML you see is due to Groundspeak's incompetence and failure to thoroughly test the recent site updates/changes/downgrades and is not a reflection on the abilities of the owner of this cache. To help us resolve these issues, please contact Groundspeak (insert Groundspeak's phone number, complaint number etc... here)"

     

    Maybe if their phones start to ring off the hook and their email boxes begin to fill, they may get the point. Disabling your caches is not something that they will see let alone make any sort of impact.

    I hate to voice a complaint but ....

    in Website

    Posted

    It appears to me that the new design has been done by persons who are not regular users of the site.

    I believe that sums up the problem quite well. ;)

     

    Quite true.. In addition, had this site been altered by professional web designers, the site would have been designed on a parallel test system and thoroughly tested, debugged and visually inspected LONG before deployment to a production environment.

     

    As an IT Consultant, Systems Engineer and Network Specialist, I would be fired if I had permitted such a disruption to a client's web presence.

    Release Notes 1/12/10

    in Website

    Posted

    Before anyone gets too upset, remember that Groundspeak relies on programmers and are at their mercy.

     

    I have worked with computer programmers a lot. Some of them are just Divas and can do no wrong (in their own inflated ego) and will "fix" things that were never broken.

    Sometimes programmers will even push changes they want, claiming they are necessary for the new feature or fix.

     

    Programmers have also been known to believe that they can do no wrong and will roll out an update, overwriting all previous code without backing up the old code. In situations like that, there are ALWAYS issues and the customers suffer.

     

    I sure hope it isn't the case but its possible that all of our complaints are not falling on deaf ears but that Geoundspeak is helpless to do anything about them until they hire new programmers.

     

    I still think the visual layout changes suck and see no reason why they would have needed to be changed in any coding work, aside from the possibility that a programmer was just trying to look busy.

     

    And those same programmers should not be compensated until such problems are resolved. This all would have been irrelevant had the new site been thoroughly tested on a parallel test system.

    Release Notes 1/12/10

    in Website

    Posted · Edited by Zop

    The problem I have with the layout is what use to be a nice neat concise one line display is now at least two lines with lots of white space before and after. On my profile page I use to have lots of caches listed on one screen, now I only have a few and have to scroll for ever to see the list. Other pages suffers from poor layout. I bet if the forum had the same layout you would notice it and not like it. Jim
    I'm wondering if we're seen the same thing, Jim. Your profile page looks very normal to me. Would you care to post a screenshot and I'll validate if that looks different?

     

    Here's what I see:

    whitespace.jpg

     

    The rows are way too tall, the columns are too long in some areas and too short in others. The right most column is nearly 2x the width as before and the View Log column is now two lines. Sure fixing the column width on the view log column would help but it still leaves too much whitespace above and below the text in the columns.

    Usage of the hint field when placing a cache.

    in General geocaching topics

    Posted

    A useless hint is not a Listing Guidelines issue, but it is a procedural issue that the Volunteer Cache Reviewer can write an advisory note about before publishing the cache. Like the common practice of reminding hiders of one-star terrain caches that they ought to be handicapped accessible, reviewers do not delay publication of a cache solely because it has a useless hint.

     

    Many reviewers leave a "form letter" reviewer note right before publication, similar to the one I use:

    Hello,

     

    Your cache will be published momentarily, but before doing so I wanted to write and encourage you to reconsider the encrypted hint section of your cache page. Your hint did not seem like it would be useful to someone decoding it in the field. From the instructions for hiding a cache:

     

    "Enter any hints or spoiler information below. This information will be encrypted on the site until a geocacher clicks on a link to unencrypt it, or decodes it on the trail. Text within brackets [like this] will not be encrypted. Please keep your hints short, so decoding it on the trail is easier. If you don't have a hint, leave it blank."

     

    Thank you for considering this request. Enjoy the logs on your new cache!

     

    Keystone

    Geocaching.com Volunteer Cache Reviewer

    I would say that this is one of my ten most commonly used reviewer note templates.

     

    I'd hate to make more work for the volunteer reviewers but this would be an ideal answer to the issue. How can we get word to request that the VOLUNTEER reviewer take the time to examine the hint field?

     

    Also, since there really isn't any way to prevent a cache owner from editing the hint once the cache is published, maybe something could eventually be added to the guidelines as a reminder?

    Usage of the hint field when placing a cache.

    in General geocaching topics

    Posted

    I was looking for a cache after midnight today and starting getting a little miffed.

    It was raining and cold. The area around the cache location was fairly swampy. GZ coords didn't lead to anything that looked like a cache location. Previous logs mentioned alternate coords. Tried those, nothing working.

    I go to look at the hint and it says "Only after logging a DNF"

     

    That's NOT a hint folks. What that does is just raise the blood pressure a little more. That "hint" is nothing more than a control issue. That cache is on my official ignore list.

     

    That's one I hate as well. That or the ever so popular "email me for hint" or"None need" or "Come on , YOU need a hint?"

     

    I guess I need to just start using ignore lists for users, not just caches.

    Upgrade Priorities

    in Website

    Posted

     

    Bottom line is it's in our best interest to give the people what they want. What's good for you is good for Groundspeak is good for you. I also happen to enjoy serving people so I have a personal interest in making you happy.

     

     

    We would really like to believe this however to see a functional production site replaced with a buggy beta site with tons of visible front-end and not so visible back-end scripting errors leads us to disbelieve.

     

    Perhaps in the future TPTB may consider thoroughly testing on a parallel test system before cut-over?

    Release Notes 1/12/10

    in Website

    Posted

     

    Please assure me they have more than one server. Can you magine if the computer crashed? One server would be INSANE!

    I hope you are wrong.

     

    This is NOT an IF, rather a WHEN.

     

    There certainly is more than one server. however perhaps not redudant servers for each service hosted. (Back end Imagry server, back end Database Server, Front end Web Server, Email server etc...)

     

    We learned however back when there was a fire in the building hosting the NOC that there is a single point of failure that needs to be addressed and to me, should have been addressed long before pooching the appearance and functionality of a global site.

    Release Notes 1/12/10

    in Website

    Posted

    Thank you for the great replies. I was prepared to hear about these bugs and apologize for the inconvenience.

     

    Design feedback is appreciated, but I'm sure you understand the priority at the moment is for broken functionality. Feel free to voice your feedback but please don't expect a reply yet.

     

    Nudecacher and missionMode, please leave those PQ titles alone for the moment as I've used them as examples in the bug doc. Thanks.

     

    I have bugs open for the rest of your reports as well, and will update you on their status when I am able.

     

    Curious... If it was known that the scripting flaws would cause such a problem, why push the update before at least the design coding issues were resolved? Are you moonlighting for Microsoft? <_<

    Release Notes 1/12/10

    in Website

    Posted · Edited by Zop

    Way too much whitespace in the new layout. Otherwise it looks like a good re-skin, and I see that the HTML has been simplified quite a bit. Also, that is quite a long list of little touchups that will be appreciated.

     

    I have to agree. Way too much whitespace and now the columns are wrapping dut to my low resolution 1600x1200 resolution. (read normal screen) I really feel sorry for anyone with less than perfect vision who needs to use a lower 1024x768 resolution.

     

    It does seem a bit zippier though.

     

    Anyway to trim back the right column to maximize the left on the My Profile page? It wouldn't hurt to strip the grid lines either.

     

    (edit to correct my rez to 1600x1200)

    Feature Request: Remove (part of) EXIF data on pictures

    in Website

    Posted

    More and more photocameras include EXIF data (like e.g. the Oregon 550(T), Apple iPhone 3GS). In that data there are a lot of nice info's: author, camera model, shutter speed; but also less nice things like: serial number and GPS location.

    So if you make a photo of the cache you also record the exact position of the place where you made the foto; which is nice for your personal archive.

    Most people are unaware this information is also included when you upload the photo to geocaching.com, probably giving away the endpoint of a 5-star mysterie cache.

     

    Could we have an option on uploading a photo to remove the EXIF info (default checked); either all EXIF info, or at least the GPS position?

    Or after uploading get a warning when GPS location is included and the option to remove it ?

     

    [edit: added iPhone]

     

    I don't believe this would be a good idea. As others have pointed out, EXIF is used from time to time for puzzle caches. It's easy enough to purge your own EXIF from pictures you take. Why not simply do so as part of your process before uploading?

×
×
  • Create New...