darus67

Fortunately for the rest of us, only a small percentage of people suck that bad.

Geeze. There must have been some sort of government comittee involved in that process.

I'd use a bigger bill, depending on how far apart I managed to release them. Across town, 1$ Across the state, $5 Coast to coast, $20 or something like that I wouldn't just toss half buck in the cache. I would put it in some sort of container (I was thinking of a baseball card holder) with a note explaining the goal. Defacing U.S. currency is only a crime if done with fraudulent intent, according to what I've read. There's no fraud here. Nothing a little scotch tape couldn't fix.

Each half of the bill is made into a travel bug. Whoever unites the two halves gets to spend the dollar. I wouldn't attach the actual travel bug tags, but I'd use numbers from tags I have purchased. That way after someone finds both halves, I can just re-use the same pair of TB numbers and launch another bill. The bug pages would, of course, contain links to the other bug in the pair. Would people actually move these, or would they hold half, and hope the other half moved to them?

Excellent series of books for the resourceful DIYer. I have the first 2. If you want to do a 1 shot experiment at melting aluminum with little investment necessary check out my Coffe Can foundry

It could be another cacher's Sig (short for signature) item. Cachers sometimes leave an item with their caching handle and/or icon behind in caches they find. Some people use a business-card-type card as their sig item. It is generally acceptable to trade for these sig items. Check the previous logs to see if any of the previous finders' handles have anything to do with asteroids or comets and the number 6

Too bad the DNR doesn't allow geocaches to be hidden in MN State Parks.

You forgot the raised eyebrow in the J-Smile coin design

Very nice! Oh, and the shirts and stuff are good, too.

I use GPXSonar, also. It can search, sort, slice & dice, almost like GSAK. I tend to carry large GPX files (500 waypoints) around with me. That way I have coverage for all of the area I'm likely to be in, on a daily basis, and can grab a cache of opportunity if I have the chance. If you only load up the 5 or 10 caches you plan to do in 1 day, converting to HTML is probably just fine.

I have a Dell Axim PPC which I use for paperless caching and navigation. I use a Garmin Geko 201 GPS with a serial cable to connect it to the Axim. When I get to the parking spot I can unplug the Geko and take it in the field while leaving the fragile PPC in the car.

Its probably fine, right up until someone drops the keyring travelbug INTO the cache after finding and opening it...

I've often wondered why this feature is not included in PQs. They have the "search from home coordinates" link on your account details page. Why not in PQs? It seems like an obvious feature.

Would you happen to have a GSAK macro that performs this task?

How 'bout this: Make a replica of my real coin, (repli-coin?) but obscure the tracking number, then attach a travel bug tag to the replicoin and send IT out as a travel bug. Would that annoy EVERYONE in one swell foop?

I'd like way to distinguish my outstanding DNFs from the ones I eventually found.

Yea, I guess obfuscating the punctuation would be a bit over the top. I have run across hints which consisted of ONLY numbers, where it appeared that the hider either didn't notice or didn't care that the hint was not obfuscated.

Make a public bookmark list, add this cache to it, and write your comments about the cache in the bookmark, for all to see. The cache owner can't delete comments from your bookmark list.

You can get there in a round about way. GPSBabel can convert from gpx to HTML and there are numerous ways to convert HTML to PDF.

Yea, spelling out numbers is a work around, but is less easy in the field. And spelling out the punctuation is really annoying. I was thinking something like this: A B C D E F G H I J K L M 1 2 3 4 5 ! @ # $ % - _ . , ; ' N O P Q R S T U V W X Y Z 6 7 8 9 0 ^ & * ( ) = + / ? : " This keeps the traditional ROT13 the same for the letters (That way the people who can already read ROT13 directly aren't inconvenienced. ) and just adds on numbers and punctuation.

The current hint encryption is somewhat limited in that it only encrypts alphabetic characters. Numbers and punctuation are left untouched. I understand the need to keep it simple to decode in the field, but I can't help wondering whether it is worth expanding the encryption scheme a bit. Thoughts, anyone?

"The Society that Hides Things" Sounds like something out of a Monty Python sketch. I like it!

Would a radar gun IN the car, pointed at a fixed object give a useful reading? Failing that, how about a radar gun in a fixed location driving a 4 foot high external display, or something, that the driver can read from 1/2 mile away.

Wow. There is definately something wierd going on with some of the map data Google is showing through this interface. If you look here: GC Google Map The area shown as "Anoka Public Golf Course" is NOT a golf course. The grey area just north of the aleged golf course IS actually Anoka High School, but the grey area just south which is also labeled as "Anoka High School" is actually a state chemical dependency treatement center, AKA "Spin Dry" Now compare it to the regular google map of the same area here: Stock Google Map None of the 3 areas I mentioned are highlighted in any way on this version of the map. 'sup with Google?

SWEEEEET!! There are a few kinks to work out yet, but its a very cool addition to the site.