Jump to content

JeremyR

+Premium Members
  • Posts

    491
  • Joined

  • Last visited

Everything posted by JeremyR

  1. This is where the ability to transfer ownership would come in Funny you should say that. I just tried to move a coin that was transferred to my ownership to my own collection and while the option to set it's collectible status is there (and enabled), I can't enter a Move to my Collection log - it's just not in the drop-down list of log types. The coin is in my possession (it's the only coin still in my inventory that I haven't been able to move to my collection) and is owned by my account, it's set to collectible. The only thing that's different is that it wasn't my coin originally. It was adopted to my account just over a year ago:
  2. I don't see anything weird myself. Care to post a screenshot? Guessing a bit, does this ring true? (a) You've found a cache that was listed at those precise coordinates before now and ( You're using Lil Devil's map enhancements Greasemonkey script to remove the small white box that normally surrounds cache icons on the Google map to stop them overlapping each other? So basically what you're seeing is the found it smiley icon with a puzzle cache icon overlaid directly on top? Just a guess...
  3. Just because we already do it doesn't make it a good idea when there's an alternative and yes, I'm sure we all trust GSAK but it's not the only caching application out there. If you look at the bigger picture, sites where you previously would have shared your login details to allow third-party access (think Flickr, Twitter, Facebook...) are all moving to token-based authentication where you don't have to give your credentials to the third party & there's a good reason for it - common sense (see oauth for more). [edit] what DunkleAura said. That's twice I've managed that this afternoon
  4. Being the Devil's advocate, the problem with HTTP authentication is that it sends the username and password in the clear. Not to mention that it would require the disclosure of credentials to third party apps. One of these problems is easily mitigated with HTTPS but the second is a problem. Option 4 would be to include a single-use token in the headers of each 'PQ ready' email that would allow one (successful) download of the PQ without a login or knowledge of it's GUID. [edit] Basically what dfx just said There are probably countless other options that would also allow an automated retrieval without enabling PQ sharing.
  5. Ok, I have a question for the powers that be, if I may. Consider this setup (hypothetical!): Firefox opens /pocket/ (user logged in previously and used 'remember me'). Greasemonkey script detects a PQ is ready and initiates the download. Firefox is set up to automatically open ZIP archives (no prompt) with an app that extracts the GPX file, invokes GPSBabel and sends the waypoints to the GPS receiver. So, is that a TOU violation in Groundspeak's eyes? My instinct says 'no', it's just a GM script and careful browser configuration. But what if the process was invoked by a scheduled task or perhaps even an email filter that detects the 'your PQ is ready' email?
  6. Please don't make it just for GSAK users though - as I'm sure you know, some of us are geeks and have our own custom setups. As was (and still is for <=500 PQs), the waypoints will find their way from the inbox to the GPSr all by themselves without me needing to intervene (assuming I remember to leave it plugged in ). I can't do that right now for >500 PQs. Allowing exactly one successful download of each PQ generated without a login and including the PQ's GUID in the email would be a great solution. Although I appreciate it wouldn't be a walk in the park technically (more counting and checking always adds more complexity, I know that), it couldn't be easily abused and would allow those of us with nerdy custom automated GPSr update routines to utilise PQ1K as well
  7. Use: http://coord.info/GCxxxxx where GCxxxxx is the number of the cache you want to link to. No setup required, it will automatically send the user to the right cache page. In your cache listing: <a href="http://coord.info/GCxxxxx">Link title text here</a> and make sure you tick the 'The descriptions below are in HTML' box
  8. OK, I've been watching this thread for a couple of days now and I'm seeing quite a bit of finger pointing from TPTB at Greasemonkey. Lil Devil made a point and now I'd like to reiterate - I cannot think of a single popular Geocaching Greasemonkey script that hits a Groundspeak domain with even a single request. Most simply rearrange or modify existing page elements and/or incorporate data from outside geocaching.com (like additional mapping, etc) into the page. So, I'd like to request that the lackeys show us a list of these scripts that you say are hitting the site. If you can show me a script that hits the site, I for one will stop using it. If you can't, quit pointing the finger at a legitimate browser extension and the authors who put so much work into improving the site's usability for our benefit!
  9. Quick fix - wrap each short word in quotes - they count towards the five letter minimum For instance, "ammo" "can" won't be rejected. (edited for better example)
  10. Don't think so. At least I've never seen any in this little corner of the US. They look like this and grow in just about any corner you can hide a cache in Don't touch - it stings a lot like a mild brush with poison ivy (but only lasts an hour most of the time):
  11. how does that tell me is not available due to tide? It doesn't. It says: "Not available at all times, so read the cache listing to find out why."
  12. Remember that most quickie conversions from WGS-84 (lat/lon coords) to OSGB-36 (grid ref) are approximate and can be quite inaccurate (can be several metres or more). If you need accurate conversion, this tool from the OS is where you need to look. Its disclaimer warns you that it could be as much as 2cm out
  13. The other solution is to let Google or another search engine handle your query - they're generally better than the in-house search system anyway. Use a query like this: site:forums.groundspeak.com national park And you should find what you're after...
  14. Hit the pause button and wait for it to download some before you start watching
  15. This is the second report we've had of registration problems so 'tis being looked into. In the meantime, if you drop me a PM (on here ) with your choice of username, we can set up an account for you manually
  16. I'd like to report watchlist trackable emails as being MIA too - I've not received at least four or five that I should have gotten today. I control the email server they're supposed to be going to so I know they're not being spam filtered.
  17. Aaaaanyway, somewhere back on topic, the golden rules of the game are this: Sign the logbook. Take and leave something if you want. Write about it online. If they don't do the first and most important of the three, then delete the log. Simple as that. It could be argued that you're required to delete the log as part of your cache maintenance duties: I also agree that you need to take some action on your listing to make it clear there's something extra. Either make it a puzzle/unknown (reviewer help required to do that) or up the difficulty rating. People could justifiably expect to walk up to a 2-star diff rated cache, find it and sign it without any problem. If people seek a 4-star diff rated cache expecting to be able to just walk up and sign it, that's their own silly fault if they get there and find they can't
  18. I don't think it will matter if what the name is changed to, to be honest, I suspect most people will still call it an 'SBA' [should Be Archived] log rather than Needs Archived or whatever else. I think it's the perceived (!) act of being 'grassed on' that tends to raise hackles, not the name of the log type. I suspect there are also technical considerations - the log type 'display name' is all that identifies the log type inside GPX files. This is something Groundspeak really should rectify by including some form of numeric identifier but as it stands, changing the log type name would break existing GPX handlers' ability to detect an NA log. It could be argued that this isn't that relevant because it's a rare log to use but it's a point none the less
  19. Can I be the first to say "Huh?!"
  20. No, I believe it has some form of private API access. Aside from being a disallowed, scraping is a terrible way for software to attempt to obtain data from a website. The slightest design change on the site can cripple the process completely (which is presumably what happened in this case). Yep, maybe even by using GPX like the rest of us developers who try to play by the rules
  21. Any chance of a fix on the <br> and <hr> tag issues? <br> works but <br/> (the proper way ) doesn't on TB descriptions (caches don't seem to be affected) Neither <hr> nor <hr/> work on TB or cache pages. Is this a bug or is that element a gonner? [edit to add] see description for TB1RTCR for a demo of what I mean. Also, a bug report that I didn't see last night (so maybe a result of this latest rollout just now?): I can't edit a puzzle cache listing at the moment (GC1WPF0 if it matters) without ticking the box to say I agree to the Earthcache guidelines. Surely that box shouldn't be visible for other cache types or at least shouldn't need to be ticked for other cache types?
  22. That sounds a touch arrogant to say the least. I'll hold my tongue until I've considered my thoughts a little more though. Arrogant? Lol. As soon as I saw 'greasemonkey' in the title of the post, i figured GS was finally going to try to ban it. What's arrogant is the part I've bolded. People put many hours work into GM scripts & GSP implying that they're going to take the best, integrate them into the site and leave the original author's work "obsolete" (presumably without credit or compensation) is arrogant. Now I've only put in a handful of hours over the last couple of years on GM scripts that are used by a few people here and there. I have no idea how the authors of widely used, complex and well loved scripts feel about their countless hours of work being made "obsolete". As you said, you can't ban client-side technology. On the plus side, I'm very pleased to see GPX attributes return, thank you!
  23. You're not going to get much sympathy and you're certainly not going to get any lee-way. The 'caches that solicit' requirement is a golden rule. Remove the text as requested and move on. You won't win.
×
×
  • Create New...