Jump to content


+Premium Members
  • Posts

  • Joined

  • Last visited

Everything posted by ChileHead

  1. The game of "reviewer battleship" happens so much I even made a cache poking fun at it, where you have to play an actual game of battleship in order to find the cache: http://coord.info/GC2XBTG
  2. The search page is nice, but until it can generate PQs I don't find it useful. I played with it when it was first release, but haven't used it since. Everything, and I mean everything, I do is based around pocket queries. My new landing page is search, but I probably wouldn't have noticed it without these release notes as I usually go to geocaching.com/my as my default.
  3. As far as I know, I haven't used any html/bbcode in any of my old logs, so I won't be going back to check them. But it would be nice if there was some way for the system to notify me if any of my old logs have unintentional markdown syntax, just so that I could go back and verify/fix them when needed. Or better yet just have the flag requested so that old logs are rendered as plain text. But I won't be losing any sleep over any old logs that might have wonky unintended formatting.
  4. I was in England, France, Germany and Italy this summer with a pitiful bit of German and French, also native English speakers. Because geocaching was not the primary reason for trip, I only loaded up my GPS with traditional caches. In most cases, I didn't need the cache description in English (though many had it anyway.) If I needed a hint, I could try and translate the hint while out, but usually didn't bother.
  5. Their implementation is likely some sort of .NET implementation. The 3rd parties out there likely use a combination of java, php, node.js, C#/.NET. There is no implementation that would work with everybody, and their implementation probably has geocaching.com specific ties into back end services that they wouldn't want to expose. The nice thing about markdown is that it degrades nicely. On a device (such as a GPS), I'd much rather see "I'm so great, I was *FTF* on the cache" than "I'm so great, I was <i>FTF</i> on the cache". So getting the "raw" logs is the best way of handling this, as the 3rd party software stack is likely to be completely different than geocaching.com's.
  6. I can understand being concerned about existing logs using legacy markup and how they render. A switch to render the old way if last modification date was older than yesterday. But I don't understand your comment about plain/dull logs. Why would the removal of html/bbcode impact your ability to write longer logs?
  7. Actually no, they don't have to understand markdown. The intent with Markdown is that it degrades nicely. That is, it displays in a readable format on web pages, mobile, and hand held devices. They don't need to understand markdown. If they do understand markdown, then it's a bonus and you get the extra formatting.
  8. I seriously anybody from HQ would speculate on such an open ended question. What organization? Does it meet the strategic direction HQ wants to go? Is there money involved? What's the positive impact to the game, what's the positive impact to the partner? Speculating on what ifs isn't useful.
  9. This might not be a problem, as although it displays as italic, the underlying text in the log is still {*FTF*}, and I would guess that the API pulls down the underlying text and so Project-GC et all will still see it as an FTF tag and record it as such. That is what I would assume. If you use the API to download then you'll get the raw markdown text, which is {*FTF*}. Everything should work fine. If you use something that screen scrapes, then all bets are off as the formatted would have been applied.
  10. There is a standard for saying you are FTF? I don't think I've seen that syntax. Most people, on my caches, just say FTF.
  11. Cool ... I had thought about doing something similar to that, mostly for play. I don't care enough to keep the notifications long term, I only want to read them, then delete (without all the extra scrolling and white space.) I have a change to my original script that will "fix" the problem if you get more than 100 emails in a day. It's not really a fix though - it just moves the original back into the inbox once you exceed the limit, so you don't lose anything. I'll post that later. I'd rather have a switch on geocaching.com for my notifications though.
  12. If they were ever to come back, I'd rather see them brought back in categories like earthcaches. History virtuals, biological virtuals, art virtuals, etc ... Each would have strict rules for what is acceptable like an earthcache. Otherwise we'd see tons of completely lame virtuals on every corner saying "Tell me the color of the street sign". The Waymarking model would work well for this, with dedicated reviewers for each category where waymarks get voted up/down, sent back if missing information. This fixes, sort of, the "wow" factor from the 2002-2003 era.
  13. You can add caches to an ignore list, but you can't ignore a single cacher. However, I believe that is a premium member feature.
  14. Unfortunately for you it does look like there are a lot of premium member caches in your area. In my area it's much, much lower, and the ratio varies quite a bit. Remember that these listings are owned by the geocachers. They make their caches premium for many reasons. The most common reason I've seen is that they believe (true or not) that doing so will make cache maintenance easier. They will have less visits for sure, but they will also have visits from more committed geocachers. Don't take that the wrong way - you can be a committed geocacher without being a premium member, but it's much less likely that a premium member would pay the fee without being committed to the game. With the advent of smart phones, the barrier to entry is much smaller than it used to be. In years past if you wanted to find a cache, you had to invest in a hand held GPS that most people didn't have. That was a $200 or more investment just for geocaching. Now that so many people have a smart phone, all you need to do is download an app to get started. I have made some of my caches premium as I've seen caches not replaced properly by newbie cachers who downloaded the app, found a couple caches, and left the game. I'd rather not keep replacing caches, so I make some of my easier ones premium. I keep the harder ones open to all, as that will weed out the cacher just starting.
  15. Understood ... my "solution" is nothing more than a hack for those of us comfortable with making such changes. I don't expect a whole lot of non-tech weenies to use it. Just something I wanted to share since it works for me. Unfortunately your solution is not working too... It worked from start, but after couple of hours I've received this message: "Service was initiated in one day more times than allowed". Is somebody from GS reading this topic? It would be great, if there will be at least some official response... I found out today there is a 100 email per day limit using the google apps script, so if you receive a lot of messages that's probably why it stopped working and you got that message. I'm going to change the script to handle that, but it won't be able to reformat after 100 emails.
  16. I didn't know that. I guess I haven't received that many emails yet in a day. Wonder if there is an alternative to edit in place (I couldn't find one before.) Thanks for pointing that out, I must have missed it. I couldn't edit the original post, so I deleted it. Here's the updated script for anybody interested (if the 100 per day limit isn't an issue): function process() { var labelName="ToBeStripped"; var label = GmailApp.getUserLabelByName(labelName); var threads = label.getThreads(); for (var i=0; i<threads.length; i++) { var msgs = threads[i].getMessages(); for (var m=0; m<msgs.length; m++) { var msg = msgs[m]; if (! msg.isInTrash()) { var body = msg.getBody(); var subject = msg.getSubject(); var textBody = ""; var lines = body.split("\n"); for (var l=0; l<lines.length; l++) { var line = lines[l]; if (line.indexOf("Logged by") != -1 || line.indexOf("has a new log") != -1 || line.indexOf("Log Type") != -1 || line.indexOf("Date:") != -1 || line.indexOf("Location:") != -1 || line.indexOf("Name:") != -1 || line.indexOf("Distance:") != -1 || line.indexOf("Created by:") != -1 || line.indexOf("Type:") != -1) textBody = textBody + line; else if (line.indexOf("Log</a>:</strong>") != -1) textBody = textBody + lines[l+1]; else if (line.indexOf("Remove this from my watchlist") != -1) textBody = textBody + "<br>" + line; } // textBody and htmlBody are the same for now, but both stripped down versions of the original GmailApp.sendEmail('YOUR_EMAIL_HERE', subject, textBody, { htmlBody: textBody }); GmailApp.moveMessageToTrash(msg); } } } };
  17. Sure, the number of caches impacted will be greater than the number of logs impacted. But over time these will slide down to the bottom of a cache page and almost nobody will ever actually see it. Let's be real - for the most part (there are exceptions) most caches pages don't have any logs read other than the last half dozen or so. These will always be "good" unless somebody insists on typing in html/bbcode that doesn't render. When I look at a cache to do, I'll look at the location, the description, and probably the last 4-5 logs. I'm not going to go back in history and read anything else unless it's one of the rare exception caches. While it would be nice for everything to either be reformatted, or have a flag to support old logs, the cost/benefit probably just isn't there.
  18. Understood ... my "solution" is nothing more than a hack for those of us comfortable with making such changes. I don't expect a whole lot of non-tech weenies to use it. Just something I wanted to share since it works for me.
  19. Yes, all messages/mails have the ToBeStripped tag but the script doesn't work. I run it, but nothing happens. Every minute is set also. OK, the email filter is working fine setting the tag. If you go back into the script edit mode, select "View -> Execution transcript" ... does it show anything? It should show you when it ran, and any errors (maybe) that may have occurred. Doh! I think I know why you can't run it. You are German, correct? Then I assume your email notifications come translated. So if you look at the script, I'm looking for English strings, and it would not likely match. Let me see if I can make this more generic, though I'm not sure I can. Alternatively you can change the English strings in the script to be the German ones you get. There may be some other multinat preference that messes with the script as well. Edit: Nevermind ... I changed my preferences to German and the notes still come as English. I would have thought that would be translated.
  20. Yes, all messages/mails have the ToBeStripped tag but the script doesn't work. I run it, but nothing happens. Every minute is set also. OK, the email filter is working fine setting the tag. If you go back into the script edit mode, select "View -> Execution transcript" ... does it show anything? It should show you when it ran, and any errors (maybe) that may have occurred.
  21. BTW this works with new cache notifications as well if you set up an additional filter to apply the label. But I wouldn't recommend if you are a FTF hound as it delays you by 1 precious minute.
  22. "You" don't run it, it runs automatically. If you have it set up like mine, then it runs every minute, so the max is 86400 times per day.
  23. You're kidding, right? It seems clear to me that extent of the "research" was someone in charge said, "We need to 'brand' the e-mail we send," and the UX guy ("Team"? Kidding again?) said, "Yessir." Less clear to me is whether this last change was someone in charge saying "Time to rebrand" or the UX guy getting bored and tweaking it in his spare time. Obviously you don't work in the industry. I do. I've been writing user interfaces for nearly 30 years, and I know how the process works at most companies. I don't know the details at geocaching.com, but I do know they have a UX team who is responsible for things like this. By no means am I defending the result, as it's clear I don't like it. But they are the ones that have the results of usability studies and where the industry is going.
  24. Are you only seeing the original and it doesn't have the ToBeStripped tag on it? If so, then likely the gmail filter didn't find the messages and apply the tag. If gmail doesn't apply the tag, then the script won't run. Are you only seeing the original and it has the ToBeStripped tag but nothing else happened? (check "all" mail, not just "inbox" in case the filter ran and archived the note.) Then the script probably didn't run. Make sure you applied the "run every minute" rule after you had saved the script. Are you not seeing the original at all? If not, check your trash. If it's in the trash then the script ran but probably didn't forward it on. Check the end of the script to make sure you put in your email. If you have to check the script, go to http://www.google.com/script, click on "File -> Open" and find your script. Odd thing is that sometimes if I click the script it doesn't know what to do, but if I right click the script and say "open with google apps script" it works.
  25. I think that's unfair and untrue. Unless you happen to work at Groundspeak, you really have no idea what sort of usability testing, focus groups, and input they get from real geocachers. I am very sure that the UX team does get input from real geocachers. Just because we don't have visibility into it doesn't mean it doesn't happen. I know how these usability studies run (generically, not specifically to geocaching.com), and I know they target various types of users. I'd love to see comments from a lackey confirming this, but I'll bet anybody a beer that these sorts of changes aren't just tossed in randomly. People that participate in the geocaching forums are almost always the longer term, hard core, and obsessed cachers. They are power users, and will not appreciate changes made to make it easier for new users. I didn't like the original HTML changes 2 years ago, and I don't like the ones made last week. But I accept that I'm not the only user they are targeting. Most comments here are from people caching since 2006 and earlier. I've been caching since 2003, and reviewing since 2006 - I'm in the minority and while I'd love the world to revolve around my process (please!), it doesn't. All that said, I would obviously like to see something different, otherwise I wouldn't have hacked up a script to make this work for me.
  • Create New...