geobrian-

Spotted on the BBC News website: http://www.bbc.co.uk/news/uk-england-humber-38922553 "CCTV operators called police when they spotted a man placing an object under a seat in the city's Whitefriargate in the early hours. Officers said they found a "small device covered in camouflage material" under the bench. It was identified as a being part of a Geocache game, where players track down online clues and hunt for hidden boxes using GPS devices."

There's also the safety aspect to consider. On a roundabout with pedestrian access across it, there's often a footpath or some other similar crossing point available on the roadside. Where this is not the case, then any pedestrian takes a risk in crossing onto the roundabout. Now would the CO like to be held responsible if said pedestrian were to be injured in attempting to retrieve their 'trinket' just to gain a brownie point? Personally, I'd rather play safe than sorry and if there is no valid path across a roundabout (and I don't consider worn-away grass as a valid designated path either), I wouldn't even consider placing a cache in that location, even if it was the only site in the locality where you get outstanding views of the local countryside etc.

Have a look at www.tb-run.com. It's a site that allows you to set up races (using your Groundspeak log-in) and follow the progress of the various TB entries. The South-East London, Bromley & Croydon (SELBAC) group used this site to set-up and track a Christmas TB race back in Dec 2010 (Gosh! Was it *really* that long ago? )

Hi Matt. I use Visa Debit to renew my membership and have had no problems. A straight forward transaction. Brian

Downloaded and installed. Thanks Mark, makes the logs looks much tidier. Brian.

I'd agree with this approach, not only for logs but for forum posts as well. Not only does it avoid problems with slow site access times, but also overcomes the standard 'server time out' problems if you're a a bit slow on the typing speed. It doesn't help overcome the typing errors that you only spot once you've pressed the 'send' button though ..

I attempted the "Kiss a frog" challenge, but when I kissed the frog, it turned into a Princess who refused to have her picture taken in case it reversed the spell and she became a frog again. How do I claim this as a 'find'? Maybe I'll have better luck with the 'find a unicorn' challenge.... :)

Confirmed, the above also works in Firefox6 - thanks.

Same display issue in firefox6 (Linux Ubuntu)

Just had my renewal processed: $30 @ exchange rate of 1.6295; charge of £1.25 plus 0.51p ertf (exchange rate transfer fee). Total for this year = £20.17. Hope this helps.

Firstly, welcome to the hobby/addiction When I took out my first premium membership last year using a Visa debit card, the amount deducted was the exchange rate equivalent to $30. There may well have been a surcharge, but I don't recall what it was. The process itself was completed without any hassle, just filled in the required details and let the system do its bits. The renewal has been done today (automatically as I'd ticked the box for recurring renewal) so I won't know the exact amount debited until the transaction is processed by the bank, but I'll make a point of looking at the detail to see if/what any surcharge may have been and post here for info. Have fun and happy caching Geobrian- (UK)

If it's booked as 'wait and return', let's hope it's a quick find

No, because if I look at the list of somebody's finds, I want to see when this person found the cache, not when anybody found it. Sorting on that column thus should work on that value also, not on something else. I can see that point, but does (did) having the option to sort my own finds by when someone else found them, 'break' the way the default option worked when searching for finds by a.n.other user? If so, I can understand why people want things left as they are now, but otherwise why not let users have the option of sorting their own finds by when others found them if they so wish?

Agreed. Don't forget, it's a toggle action - the default is the way it is now, so jholly and others would see no difference, toggle once and it sorts to when OTHERS last found (today, yesterday etc), toggle twice and it presents your finds in reverse order, and toggle again brings you back to the default setting. What I can't understand is why this particular sort [by Username (Found) - User] is disabled in this way, yet if you do a search by country, post code etc., the chronlogical sort works fine - and I don't see anybody complaining about that function. Please could some consideration be given to reinstating the same facility when using the 'By Username (Found) - User:' search, or perhaps an explanation of why it's disabled. Thanks.

It depends on what view you're in. If you look at the list of caches some user has found, then the "last found" column reflects the date when this user has found the cache, and sorting is applied on that also. If you look at any other (?) list of caches, say from a certain location, then "last found" is last found by anyone, and sorting works accordingly too. Serisouly, it's always been like that. Well at least the display, I don't know about the sorting. I'm also not sure if it also worked that way if you looked at your own list of finds, but I would think it did. I'm talking about the My Public Profile > Geocaches > All Geocache Finds page (which is basicly just a a find caches by username search result using my username. Same here - I used the sort to see if the caches I found have been logged (found) today, yesterday etc. The sort used to bring them up in chronological order (last found date, irrespective of my own find date) so that I didn't have to trawl through umpteen pages of finds to look for the most recent find. It was a useful facility to have and use.

User page - sort by 'last found' field produces an incorrect sort again. Appears to be the same bug as previously, which was cleared by a hotfix.

This still doesn't seem to be working, it's still sorting by the date I found the cache not the last found date. Likewise for me too. [uk using the dd/month/yyyy format, though it still doesn't work if I revert back to the old date format - oh and thanks for making the date format user configurable - much better ] *edited to correct typing error*

Hopefully just a bug. There was a 'hotfix' issued yesterday that was supposed to resolve this issue (amongst several others), but it still doesn't work for me either There is an ongoing topic in the Release Notes forum which might be worth keeping an eye on in regard to this and other problems with the latest upgrade. Brian

A cache should stand on its own merits, not as the result of solicitations, however well intentioned.

As I like to look at my finds to see if others have found them too, I like the option of being able to sort on last found date on my profile page (list geocaches you own/found). It saves having to trawl through a possibly extensive listing. Nice one

I think the problem is with the database rather than any phone app. Currently any entry reflects the database date/time (8 hrs behind GMT at present). What would be useful would be for all entries to be dated and timed as per the users time zone as set in user preferences. There is currently a suggestion under review on the feedback site ( click here ) for dates (and hopefully times) to be set as per users country/time zone preferences. It'd be nice to see my logs show the 'real' time they were logged, rather than that of some other time zone *edited to correct/add url code*

Blast! beaten to my own edit <grinz>

That site is a hoax - see Wikipedia:

Hee Heee .... Simple isn't it! It never occurred to me to do it that way, so thanks for mentioning it.

Much the same here, though being 10m to the south of London with only public transport to hand means that stuff 20m south of me is often not accessible, yet 20m north and I'm missing out on caches that I could conceivably travel to. So what I've done is to set my notifications on a 20m radius of Charing Cross. This at least gives me a chance to get some of the more east/north/west caches without compromising too much on the accessible ones to the south. Having said that, I've yet to claim an FTF outside my local caching area, but it's not something I'm particularly bothered about so I don't try that hard to get to them.