Jump to content

monsterbox

+Premium Members
  • Posts

    332
  • Joined

  • Last visited

Posts posted by monsterbox

  1. 11 hours ago, Team Microdot said:

    As a cache owner which would you prefer?

    • Seekers don't realise your cache is buried. As a result they post DNF's and NM's. The health score of your cache starts to fall. Seeing an accumulation of negative logs people start to steer clear of your cache.

    or

    • Seekers realise your cache is buried. They post Found It logs. The health score of your cache remains positive.

    It also wasn't allowed to dig a hole for a post or such!

    And by the way: You mention another issue: I don't really like the idea a health score drops just if someone is writing a DNF log. What about a D5 hide? Cache is there but many people just don't find it! Health score drops then? Bad idea!

  2. 15 hours ago, barefootjeff said:

    I often meet up with friends in a restaurant across the road from the local railway station but no-one has ever claimed that's a security risk. Why should a geocaching event be any different? I can understand them not wanting events inside train stations (or airports or cruise ship ports) but near them? These vicinities often have lots of cafes and restaurants where they want people to gather and enjoy themselves.

    I can't understand why an event shouldn't be possible there!? Here in Munich we do have a HUGE restaurant within the airport and many more smaller ones. Noone complains that people go there. So why shouldn't there be an event?

  3. 21 hours ago, Keystone said:

    These posts prove that it was worthwhile to add the clarifying language to the new guidelines.  There has been no change in policy, but the requirements are stated more clearly now.

    Don't believe me?  Run a search in these forums on keyword "magnet" and for posts authored by me. You will see posts I've made from 2008 to earlier this year, all of which consistently state that a magnet by itself is not a geocache, but a magnet that encloses a separate logsheet does qualify as a geocache.

    But do you consider this being a "container"? I already fear the translations :)

     

  4. On 8/27/2017 at 9:02 AM, arisoft said:

    Actually you are allowed to place the first stage further than 2 miles away. The rule applies only to the final stage as stated. For example, if the cache has three waypoints: Posted (so called bogus) coordinates, the first stage (solution for the puzzle) and the final stage (solution for the field puzzle at the first stage), then the first stage is allowed to be further than 2 miles away.

    Hmm, I don't really see how this makes sense!? Could be I wasn't clear enough in what I mean, so here's my concern again:

    1. Icon is placed somewhere
    2. Calculated FIRST stage is within 2 miles and this makes some sense for me.
    3. Final is WAY further, as there might be many stages in between, like with any normal multi.

    So why shouldn't this be allowed? There's no big difference to a normal multi. Even there a final can be so far away from the icon, there even are extra icons that for!

    I still think that the guidelines should be changed to FIRST and not FINAL stage in that point!

  5. On 8.8.2017 at 3:06 PM, arisoft said:

    Maybe the designers of this new feature think that, because it is not possible to log multiple founds, the location does not matter after the first found.But sometimes there is reasons to visit the cache again. For example, when the most wanted travel bug is placed in the cache, you definitely want to visit at the solved, not the bogus coordinates.

    But the corrected coords are still there!? So where's the real issue then? Couldn't you still navigate to these coords?

  6. Hi!

    I guess I've found an error in the guidelines for mysteries (Help center 2.2):

    " If the posted coordinates are not for the final stage, the final coordinates must be added as an additional waypoint. The final stage cannot be more than 2 miles (3.2 kilometers) from the posted coordinates. This allows the cache to show up in nearby  searches. "

    I believe that the underlined "final" should be "first" instead. Otherwise a multi also shouldn't be allowed to be longer than 2 miles... This error can be found both in the guidelines as well as in the help center!

    Bye,
    Christian


     

  7. On 22.8.2017 at 11:13 PM, plaidtopia said:

    Yikes. Ok, we'll add this to the list. Thank you!

    Hopefully, this is LESS wasted space in most people's eyes: We basically had two headers before, a white and a green one, one on top of another. This release has consolidated these into a single line, reducing our vertical header space by HALF and bringing more content "above the fold," as it were.

    As for the e-mail link, do you mean the link to mail the cache owner? If so, that's still there. Nothing should have changed down-page as a result of this release, but if something's missing that should be there, let us know!

    "Wasted space": Hmm, I was referring to the map page for instance, as this ist my most used one. The top bar is higher now, with just the same info. By accident I just had them side by side as I still had an open tab with the old style. Sorry, as I don't use a single of the newly changed pages for several reasons I can't tell if it went better there!

    Email-Link: Sorry, I'm not sure if there really was one or not. I THOUGHT there was a link like the "Message this owner" link.

    Color: Could be my exact monitor already shows green colors a bit more prominent than other monitors. But compared to the old matte green it really is sooo bright, especially at night and the contrast to the map colors is pretty big. Still don't like it that much, but that's tough luck, I guess ;)

  8. A few comments:

    1. It's wasting space again, similar to the new dashboard and such. Just don't get why the top bar needed to get higher.

    2. That new green color hurts my eyes, especially at the map page as there's more green. It looks like my screen is broken :( I way more like the more matte colors

    3. Could it be that the email link within the cache page isn't there any more!? Or do I simply just remember that wrong?

    4. The Geocaching logo as well as the big text seems to be blurry, like just been expanded. I checked the size and even if it SHOULD have been the same (196*29) it is about 10% bigger. I compared the code and it slightly changed. From absolut size to some automatic one I guess.

    5. The new dropdown menu itself seems to be ok :)

  9. On 28.7.2017 at 10:47 AM, rollinginthecache said:

    I have, sure that looks great. But if I'm on a trackables or a cach page for example, I can't get to it without clicking my name then reloading the first page.

    I'm hoping its easier to navigate such as a menu and sub-menus or it can be included in the tops of these areas LIKE the old version, for clarity. 

    They won't change EVERYTHING at the same time (hopefully ;) ). Right now they are working on the new dashboard as well as the logging page, earlier they changed the list page. And they already made a few changes to the cache page, too.

    But putting kind of every link to every single page won't happen at all, I believe. Just too much! You might simply consider using a few bookmarks for the pages you use most. My start page always is the map. Plus the OLD dashboard as 2nd tab ;)

  10. 17 hours ago, rollinginthecache said:

    Hi. I hope this is in the proper area, apologies if not, but in terms of the website homepage, I really like the "Quick View" view of the dashboard because of the ease in finding things. 

    Those places are hard to navigate to as is on PC, but in mobile its kinda luck of the draw if I get to a section. 

     

    I'd like to suggest that you make these links easier to find, maybe in a side menu on all pages or the top menu where the Sign Out/Settings is? Nothing like being a newer cacher and trying to find the page where your trackables are! Lol. Thanks and I hope to see the menu soon, ESPECIALLY in the mobile friendly version(s).. Also, the app is really lacking this feature. I'd post the same in the Android app area but since this is here might as well address it here since it ties into the website. I couldn't see where my trackables are, just ones in my inventory. Thanks 

    Capture+_2017-07-25-17-35-00.png

    Why don't you just do what the website is telling you? ;) Hint: Blue part... :P

  11. 5 hours ago, Silverheels said:

    This looked like a fun challenge for the summer; however, it is not quite clear in some of the aspects..one big question is does every person on your league have to log at least one cache and earn 5 coins (points)?  If one of the team does not, does that mean the rest of the team will not get that week's souvenir even though they all did 5 coins or more and totaled 30 or more coins (points) for the week?  Should one remove any of their team members who have not done any finds by Sunday the 23rd if all friends of the league (team) must earn at least the 5 coins (points)?  Hope can get an answer by tomorrow July 23rd!

    Hmm, I don't really understand you ;) The description clearly said that your team needs to earn at least 30 points and YOU need to earn 5 points to be eligible for the souvenir then. That clearly implicates that the team members who don't find a cache will simply not get the souvenir.

     

  12. On 13.7.2017 at 4:37 PM, Twinklekitkat said:

    This is an inquiring minds want to know kind of question. What is the sorting criteria for your crew? When looking at MY crew the people in the top spots are my friends who have found caches this week (or since the inception of the friend league). That makes sense. Now how is the rest of list of my crew determined? I realize it's only a list of 10 of my 12 friends. I get that. But how are they listed here? What's the sorting order after # of coins collected? It's not by date friended, not alpha order, not by date joined, not date last visited. What is it? Also, if more than 10 of your friends are active during the time frame, will you be able to see more than 10 slots?

    It's so easy ;) The list simply show the top gold coin earnings. And everyone of your friends does count!

    • Upvote 1
  13. Release Notes (Geocaching.com and Geocaching® app for iOS) - June 29, 2017

     

    With this release, we have updated the functionality around displaying geocaches with solved coordinates. Now, all caches with solved coordinates will display on the map at those coordinates when solved but unfound.

     

     

    Today I ran into another issue with not seeing the solved ones at the original header coords :( I need to find 10 caches places IN a river to meet the requirements for a challenge. Now that's completely tough and the only solution I came up with so far is to set up another account with zero logs an no corrected coords. That way I can again find them at the "original" spot. Just missing PMOs then :(

     

    The other issue I still have is not seeing the type of the cache any longer. I would so much prefer having the option to show corrected coords or not!

     

    Thanks,

    Christian

  14. Hi, all! I'm Nate, the PM on the project and fairly recent new addition to the Geocaching team. I hope you all like the changes to the homepage — not only does it hopefully help with faster navigation around our site and content, but it also lays the groundwork for the page to be more dynamic and fresh. I truly appreciate all the feedback or reports of issues, so keep 'em coming!

     

    Hi Nate!

     

    First of all: Welcome :)

     

    And now lets start with some feedback and I hope that Carly isn't blaming me again of bashing you ;)

     

    Ok, seriously now: The quick searches might be nice, but I would change some defaults for sure! If I would do a search I woulch right away change some filter options and only show "I have't found", "I don't own" and "Enabled" caches. I usually don't care about the others while doing such a search. And for events I would usually prefer just seeing not yet "found" ones as these are the ones in the future :)

     

    "View geocaches near you" isn't anything I would need as the map search anyways is my personal default page when opening the browser.

  15. I will also put in my 2 cents that it would be beneficial to have the icon show the cache type as well as the corrected coordinates icon. Maybe the little puzzle piece can be in the upper right or left of the cache type icon. That way you can easily see both pieces of information on the map

     

    I would just put some dots in the "corner". Different colors as well as slightly different places for DNF and Coords

  16. The puzzle piece icon should be a similar colour to the type of cache being corrected.

    Orange for multi, different colour with puzzle icon if corrected coordinates are entered for that multi.

    Blue for puzzle, different colour with puzzle icon if corrected coordinates are entered for that puzzle.

    Ditto for other types.

    That would improve things a bit, but you'd still lose the cache type shape which helps with quick identification.

     

    Personally, I think too much metadata* is being packed into one icon. It starts to get a bit silly when you're trying to depict both a Multi that you've never looked at and a Multi that you've DNFed and updated the coordinates for, all with one icon.

     

    Thankfully, I keep all my updated coordinates offline in third-party software, so I won't have to deal with the puzzle piece icons. I still have to deal with the DNF icons, though, so I'm still hoping for a more elegant solution for those.

     

    *that's a better term than "attribute" that I was using earlier

     

    A solution for DNF would be changing the default to NOT show them. That way one can toggle ON showing them but it wouldn't hurt in the PQ view

  17. Hi!

     

    1. Like with the DNF icon it has the exact same "issue": I see this new icon and don't know any more what the real cache type is. I like the idea of being able to see that, same with DNF, but just as an option please. I still am way more interested in the cache type.

     

    2. While showing a PQ on the map I see the new icons (DNF/Puzzle) but in the list I see the cache type. Not sure if that's by intention or not. And I would also like to be able to toggle DNF/Puzzle view within the PQ view, if possible!

     

    Thanks!

  18. Hi!

     

    As there was no new release note regarding the new puzzle icon on the map I simply add some comments here:

     

    1. Like with the DNF icon it has the exact same "issue": I see this new icon and don't know any more what the real cache type is. I like the idea of being able to see that, same with DNF, but just as an option please. I still am way more interested in the cache type.

     

    2. While showing a PQ on the map I see the new icons (DNF/Puzzle) but in the list I see the cache type. Not sure if that's by intention or not. And I would also like to be able to toggle DNF/Puzzle view within the PQ view, if possible!

     

    Thanks!

  19.  

    This was the original request, for context:

     

    I'd like to see an option on the iPhone app to check in users you are with so the cache logs to their account as well and everyone doesn't have to have their app open and whatnot!

     

    Thanks :) Ok, now I just wonder why the other come with her at all :P Isn't logging the cache part of the experience? At least it was at the time I started with this hobby. Nowadays it might have changed a bit and having that kind of feature an owner might only get very short TFTC logs at all :(

     

    At least this would be a feature I wouldn't care much as long as I could completely opt out

  20. It was proposed as a solution for one-off group caching trips, to facilitate ease of logging within the group.

     

    This tagging feature might be a step towards facilitating that sort of functionality.

    That could be useful, if the others who went on the geocaching trip are already members, and they're on my friends list.

     

    If they're newbies who haven't created an account yet, or if they have an account but they aren't on my friends list, then I'll have to share the list the old-fashioned way.

     

    I still don't really get it... Don't you think this feature only might make sense as long as you can be sure there's just ONE person out of the team doing this? And it also only makes sens to send field notes to someone who hasn't been logging yet? To me it looks like there are too many "ifs" in this scenario.

  21. Despite the dramatic description of the situation this is actually both easily explained and (not quite as) easily fixed. Last week (and since launch) we were ordering the logs based on the date the log was created. When you post a log we tag it with a very precise UTC based date + time. This makes sorting logs by the date very easy because the time precision nearly guarantees a unique key for everything. Now however, we are using the date the log was "found" (regardless of when the log was created). I won't go into all of the minor details because it is something that we are still trying to unwind here, but the log date often does not have a time associated with it, only the date. That means that your logs are all listed on the same date. Without a secondary sort parameter they are all tied for "most recent" so which log gets returned first is dependent on how the hamsters are feeling at the moment.

     

    In order to resolve the issue we'll simply add a secondary sort parameter that will act as a tie breaker in the case that the dates do not have enough precision to properly identify the order of the logs.

     

    Why don't you simply use the creation time stamp as secondary key? I guess this works for most of us as people usually log in order, don't you think so?

  22. I would actually prefer the logs to be ordered by the date they were posted on. A log that my friend posted a minute ago should appear on the top of my dashboard so I reliably notice it and not on the bottom just because he is a few weeks delayed with logging. It is a dashboard after all, not a cache page. The aim of the community recent logs section is to notify me about logs my friends have posted (if they agreed so in their settings). If the logs are freshly written but get buried under older ones because of their date, that goes against this purpose. One would have to scan the entire feed to (maybe) catch what's new instead of convenient check of the top of the feed.

    That makes sense, which leads to a sticky situation.

     

    When someone is viewing just their own logs, they'll usually want to see them displayed on the dates for which they were logged (not the dates on which they were submitted). However, as you pointed out, it makes more sense to see them on the submitted date when viewing the Community logs. Having these different views behave differently would like be confusing for many people, and you'd have a disconnect between the dates shown for your own logs on the two different views (ie. on Yours: date logged, on Community: date submitted).

     

    I'm not sure how to solve this while still keeping everything in one list.

     

    Hmm, even if I would like to see my friends' logs (what I don't ;) ) I would like to see them at the found date and not the logging date. This would put together all the logs for "our" trip which is the only situation i personally am interested in seeing these logs at all. And I'm simply doing this by checking the caches I visited and not via the dashboard IF I want to see the logs.

     

    Putting the logs to the logging date would complete get me confused :D

×
×
  • Create New...