Jump to content

stebu

Members
  • Posts

    279
  • Joined

  • Last visited

Posts posted by stebu

  1. 46 minutes ago, Jayeffel said:

    Can you get a special code with other than a letter or number - # $   * etc? Or are we limited numerals and letters only?

     

    One I am thinking of I will, not show because someone may see it and use before I am able! I do not see that cache code I am thinking on in use.

    No, the codes have numbers and letters A to Z without I L O V

  2. I just placed a geocache and accidentally listed the coordinates for the wrong cluster of trees, about 150 feet away. I was notified by the FTF and tried to change the coordinates using a new log, but it thinks that the new coordinates are thousands of feet away. For reference, here's the coordinates:

     

    Incorrect ones, current: N 39.06295, W 104.51132

    Correct ones: N 39.10482, W 104.85157

     

    So, in essence, the problem is that I can't change the coordinates of my cache (GC784T9) to be correct because it thinks it's thousands of feet away when in reality it's only about a hundred.

    I'm not sure about yuor notation, but:

    Old N 39.06295, W 104.51132 =N 39 06.295,W 104 51.132

    New = 39.104820,W104.851570 =N 39 06.289,W 104 51.094

     

    So if you might be able to do it, if you choose the correct representation for input coordinates.

  3. Sorry, sorry! My bad! It is shown at the solved coordinates! That's great.

     

    A mod can remove this thread.

     

    https://coord.info/GC4YGGN is shown on map only if zoomed out a lot (about same level as MO cahces), and NO it's not MO.

    Other caches are visible normally in the neighborhood.

    Win 10 and Chrome.

  4. Dashboard: I don't miss anything on the old dashboard, I only miss things on every single new page you came up with in the last time ;-) That's why I'm still using the old pages. I'm trying the new ones once a day but up to now they are still unusable for MY needs! But at least I'm still trying :) Today I haven't seen a single of MY finds in the recent logs area even if I've found 12 caches yesterday. So I'm urgently waiting for the moment I can finally turn off the other logs. But I fear I then still best case can see the logs of the last 2 days vs. the 30 in the old version. Please allows us to able to get the same options for the recents as we have with the old version. Would be more than appreciated!

     

    Currently, we are showing the most recent 20 logs. If you are finding 12 caches per day then you correctly would only see about 2 days worth when we display 20 logs. However, if we display the last 30 days then you could have 300+ logs. That makes for a much larger request to the servers which results in a slower response and takes longer to load the data.

     

    Several people have mentioned wanting to see their recent logs for the last 30 days. Assuming you are looking at only your own logs, can someone help me to understand what you are trying to achieve?

     


    •  
    • How often are you scrolling through all of those logs?
    • What are you trying to find? (i.e. updating logs, remembering recent adventures, checking your work - didn't forget anything?)
    • Do you prefer all of the data in a very long (slowly loaded) list or a shorter list that allows paging or requesting more data as needed?

    Well, I might want to know which caches I logged in June 2008. The "all your logs" page can achieve that sluggishly, but the paged approach will usually find what I need faster and with less server load.
  5. Any bets about whether GS will address the issue in our lifetimes?

    Not going to happen. The Message Center was a few fads ago, so it has completely fallen out of the minds of TPTB. They're busy breaking streamlining the cache-logging experience, and then they'll get bored with that within the next week or so and move on to another part of the website to streamline. Maybe a few years from now they'll loop back to the Message Center and replace it with another tool that doesn't work and/or doesn't do what the members need.

    You might be on to something! They just streamlined the help center and announced streamlining of the Dashboard!

    I sure hope, they get the bugs and annoyances ironed out of logging experience before it is left on its own!

  6. Why are Groundspeak doing this? Ie. moving towards a mobile only interface?

     

    1) They want to reduce the costs of having different UI to support?

    This might be offset by users quitting premium membership or quitting hiding caches due to not receiving feedback other than TFTC

     

    2) They want to make geocaching as streamlined as e.g. munzee is, where the logging is usually only an automatic "capped it" and nothing more.

    This would also reduce the amount of clever/nice hides, because of the non-existing positive feedback.

     

    3) Some other reason?

    If they would tell us, maybe we could offer some acceptable solutions. I bet the community has a lot of know-how about web and mobile app designs and most importantly they are using the systems!

     

    Just wondering if it is worth while to list my next cache?

  7. I hope you can fix this bug, also:

    I logged 4 cahces with a draft, then converted the drafts into "found it" logs, no problem.

    Later in the day (6h or so later), I logged a cache directly from the field using Locus app.

    This last log is now shown as the first log of the day! Very confusing :angry: :angry:

  8. I found about 20 caches today (wohoo!) and uploaded fieldnotes for each of them.

    When I converted them into foundit logs, two of them showed up twice, both the actual cache log and also the personal TB visit log.

    Not a biggie, I corrected the situation by deleting the extra logs. But some kind of misbehavior in the system!

     

    You seem to be describing a different situation from the referenced duplicate logging directly from the app.

    You uploaded field notes/drafts to the website and the # of field notes uploaded to the site was correct? You then created found it looks from the uploaded field notes and duplicates were created?

    If so, that might indicate an issue with the latest website update for field notes/drafts.

    You're right. I uploaded field notes(drafts) only from the field. When I edited the drafts and then submitted the log, the result was double logs twice.

    Today I logged 12 caches in similar manner and all went well.

    But there's two extra logs hidden in the system, the site claims my find count is 2 more than it actually is. When I list my finds (seek/nearest.aspx?ul=stebu) the first two pages only show 19 finds, so the two double logs are still messing up the counts!

  9. I found about 20 caches today (wohoo!) and uploaded fieldnotes for each of them.

    When I converted them into foundit logs, two of them showed up twice, both the actual cache log and also the personal TB visit log.

    Not a biggie, I corrected the situation by deleting the extra logs. But some kind of misbehavior in the system!

  10. The Message Center Indicator in the top right-hand corner shows I have a "message" waiting for me to read it.

     

    However, I don't have any unread messages. How do I get rid of the Indicator when I have no unread messages?

     

    I have a MAC; 10.10.5 OS & I use Safari as my browser.

     

    I have the same problem if I use FireFox as my browser.

    I had the same problem, until I realized that the indicator was for drafts (aka fieldnotes) :huh:

×
×
  • Create New...