Using a longer text to hide a secret text is a good way to obfuscate it. For example you can use the numerical value of the first letter of a sentence (a=1, b=2, c=3) to indicate the offset of the character to be used. That way, unless the recipient knows the pattern to look for, the message gets lost in a sea of letters.
The container can be found at:
The worst thing which can happen is that the container is missing. Lots of time is spend on searching but nothing is found. I know the feeling, it's horrible. It should be there, but it cannot be found. Assume for now that it isn't really there. For etiquette you should log it as "not found", but if you are not the first to not find it you could also log it as "needs maintenance". (Overall I log every attempt to find a container, so my list of "not found" is very large). "Needs maintenance" is a way to tell the cache owner that there is something wrong.. After a timeout with no action from the cacher owner the local reviewer will archive the cache. Identical as the action from the reviewer, the cache owner can archive the cache themselves. Owners can apply afterwards for a cache to be unarchived, but that can only be done by reviewers. Common knowledge on to prevent disappointments is to make sure that the list of caches in your location device is up to date! Geo-based games can be fun, but keep in mind that about 10% of the caches will be missing.
