Matt98030
-
Posts
18 -
Joined
-
Last visited
Posts posted by Matt98030
-
-
I've had similar problems with my TB's...
I have had several that a cacher retrieved it, and then held on to it for 6-8 months logging pages and pages of "Vistited" or "Took-It" to events. One of those cachers was holding nearly 100 TBs, and carried some of them for 18 months.
I have had a TB that suddenly started having many many "Discovered" events from all around an area, without it ever leaving a cache. I inquired with several of the cachers who had "discovered" it and most of them said they "saw it at an event", a little more investigation turned out the the person who last placed it in a cache, also held several other TB's, he would go to events with all his TB's and sheets of paper with all the TB ID's, then people would "look" at his box of TB's, take a sheet, and log all those numbers. He said he'd "accidentally" forgot to remove my TB's ID from his list, when he dropped it...
Most recently I have a TB who has been held by a cacher for 6 months with no activity, I contacted him and asked why, and he said, "there are no caches in his area large enough to hold a TB", I checked his logs, and he has logged hundreds of caches in the last 6 months, many with TB's, many that have held TB's in the past, some TB Hotels, and several ammo boxes... He's also holding 5-6 other TB's that he has had for over a year, with NO activity.
Its a mystery to me why people do things like this. I guess they think its cool to have a huge list of "discovered" TB's even thought most of them they've never really seen. And I don't understand logging hundreds of "took-it" to events at all! There is no stat to pad for taking TB's to lots of places! I blame it on GeoCachingHQ adding the button "Log all Trackables Visited" for a cache you find. So people are not really taking these TB's to all these caches, they just leave the TB's at home in a box, and click that button for every cache they find...
I've contacted GeoCachingHQ and asked what to do about these situations, and they say to contact the cacher, I've done that and gotten responses like "Mind your own business"..
All of this has really taken the fun out of TB's for me. When I first started caching I purchased several TB's and thought it would be fun to release them and see where they went, but now I'm really hesitant to ever release anymore TB's....
-
.png)
1
-
.png)
1
-
-
23 minutes ago, cerberus1 said:
The "options" would be making your trackable collectible (like folks looking to make their car or walking stick "Discover only"), as this Help Center info explains on the subject.
So I can't really control the log entry options, but I just ahve to choose between allowing all options, or only allowinng "Discover" or "Note"???
I was hoping I could remove "Visit" from my trackables....
-
4 hours ago, RuideAlmeida said:
It's an option available for the owner of the trackable.
I just tried to launch a new trackable. I see NO option to set the log entry options??
Where is it?
-
12 minutes ago, RuideAlmeida said:
It's an option available for the owner of the trackable.
Thanks!! Thats good to know!!
-
10 minutes ago, RuideAlmeida said:
Think of it this way.
A trackable belongs to somebody, it has no life or will of its own.
Drop, Retrieve and Grab are "actions" that you can perform with a trackable... and all generate a notification to the owner of both the trackable and the cache where this trackable is or was.
Visit is an action that are mostly related with the person... and do not generate any notification to others than the owner. With a reason.
Who am I to order a trackable owner to do anything different than their will, as long it doesn't abuse the system?
but the "Visits" pollute the log and make it hard to see who has actually had the trackable and where its really been. If people are visiting a trackable that never leaves home then the journey map for that trackable is fake, and the trackable really never visited any locations except for dropped lo entries. I launched a trackable and a cacher picked it up and carried it around for several months visiting caches, there were 28 pages of logs but the trackable had only been touched by about 6 cachers.. I suspect that the cacher just left the trackable at home or in the car, similar to what the OP in this thread had done.
it might be ok to do this with a trackable that you own, since no one else will ever see the trackable or care about its log..
-
1
-
-
I recently found a geocoin in a cache and retireved it. When I went to log it, the only log entry option was "Note" or "Discovered".
Can the log entry options be controlled for any trackable, and how do I do that?
-
12 minutes ago, RuideAlmeida said:
Not really, but some geocachers use a trackable to keep full mileage of all the caches they Found, with Visit logs. Since someone is the owner of a given trackable and all the logs will be in the trackable listing... and the geocacher did Found the caches, all is perfectly "legal", don't you agree?
Not really... To me "visit" means "visit"... but whatever....
-
1
-
-
I found a cache in Vienna that contained four geocoins, all the same, all with the same number.
I took one and logged it. The only log option was to "Discover" it.
In my log I said I would move it along, and the owner replied to me that there was no need to move it, that I could just keep it as souvenir, and let my friends "discover" it.
There have been several entries in the coin log since I picked it up.
I would like to do something similar, and make my own coins and pass them out as souvenirs, all with the same tracking number.
I asked HQ for some help on this and they said that wasn't how they recommended using coins.. and every coin should have a unique tracking number...
I'm relatively new to caching, and this is very confusing...
-
On 7/8/2017 at 1:25 PM, TriciaG said:
Yes, you can keep it. You can show it off at events, or stick it on a shelf, or... it's yours; do what you want with it.
I have a coin I keep at home, but I "Visit" it to every cache my husband and I find together.
You leave your coin at home? So your coin doesn't really "visit" all the caches you find does it? You visit them, but the coin doesn't, is that how this is supposed to work?
-
My trackables (the few that remain) have "Do Not Visit to caches" on the TB page. And I delete most of the 'visited' logs. Has caused some acrimony with one or more cachers. But makes the TB far easier to follow. Groundspeak has permitted me to delete those 'visited' logs.
One of my trackables has only been dropped/pickedup by 5-6 different cachers but it has 18 pages of logs, 90% of which are from the same cacher and are empty "Took it to" logs.. I don't have the time or energy to delete that many logs..
Its very dissapointing because it makes it almost impossible to see where the TB really has been, and also makes me really hesitant to ever release anymore TB's, I thought they would be fun, not just frustrating.... I wonder why Groundspeak refuses to fix this? Its not like the "Visit" logs are important to the game..
-
If visited logs stop working, or if they stop working reliably (e.g., because they're turned off on some trackables), then people will start dropping and retrieving the trackables again, like they did before visited logs were implemented. And it won't even be that much work. It's just a checkbox in whatever tool the person uses to post logs.If some people like the Visited TB feature and want to use it <or over-use it> thats fine, but I would like to have the capability to turn VISIT's OFF for my trackables, or an easy way to delete those log entries from my TB logs.And if you delete logs, then those who want to post visited logs might just repost them. IMHO, a better solution would be a filter that allows you to hide the logs you don't want to see, without deleting them for those who value them.
Well, if there isn't a way to fix this, then I am going to quit releasing trackables and will kill off the ones I have now, because it is a waste of time! I just checked one of my trackables today, it has only been picked-up/dropped by 5 different cachers but it has 18 pages of logs, 90% are empty "took it to" logs from the same cacher, and their are several duplicates....
It really takes the fun out of it, when its impossible to see who has had the cache and where its traveled to...
-
Is there anyway to delete multiple log entries for Trackable? Or is the only method to delete them one at a time?
I have pages and pages of log entries that need to be removed, doing them one at a time is tiring..
-
When I view the logs for my TBs I have only 3 or 4 valid entries and pages and pages of "visited" logs that I am not interested in, is there anywhay for me to filter the log so that I don't have to page through a large number of pages, just to see where the TB really has been?
-
I'm relatively new to caching (450 finds) and have recently released a few trackables. I was excited to get some notifications that my trackables were moving, then when I went to see where the trackable was and where it had been I found pages and pages of "Took it to" or "Visited" logs, but only 3 or 4 actual "dropped" or "retrieved" logs...
Because of the way the GS interface works for logging a find its a one-click automatic action to log ALL the trackables in your possession as having "visited" every cache find you log, whether you are actually carrying the trackable to the cache or not.
I love to see my trackables moving, but to me, fake visits because of a one-click feature of the cache find logging tool is NOT "moving", I would like to see only logs of my trackables actually moving, from place to place, and from cacher to cacher, and it seems like the "Visited" entries make that almost impossible the way it is currently implemented.
There's a bunch in another thread who believe Visited "took it to" logs are fine, and instead, Discover logs are the problem.
Different strokes...
- But I agree, without pictures, there's no evidence they even have that trackable any longer, simply the code in their inventory.
I don't believe all apps have that automatic trackable logging though, just some.
I kinda liked the trackable logs when responsible folks dropped/retrieved from a couple caches, letting the CO know they still had it without sending emails, until they'd find a nice cache to leave it.
This "visited" thing, not so much...
I only want to see logs where my TB has actually moved from one cache to another and from one cacher to another.. "Discovered" logs are ok to me, since that indicates that a person really saw my TB in a cache... "Visited" or "Took it to" logs are of no interest to me, since who knows whether the TB was really taken to that cache or it was just a button click.
-
Just one log with a nice story and a photo on my trackable per year would have meant more to me than 5000 took it to logs in year without any story.
+1
I just want to see the story of the tb without having to wade through pages and pages of blank visited logs
+1
I have a few trackables and they have really only been in a very few caches, but they each have pages and pages of blank "visited" logs, it makes it nearly impossible to really see where by TB has really been.
It would be nice it there was a way to hide "visited" logs when viewing the log entries for my TBs
-
it reflects the actual travels of the TB.
I don't believe it really does reflect the actual travels of the TB.. WWat if someone has 10 TB's in a bag in their car or at home? But for every cache find they log there is a button for "Visit" all TB's in their possession, so did the TB's really "visit" that cache?
Is it that many visits in a small area is annoying? Again, a 'usage' issue - encourage people to only use Visits for significant travels.
Yes, I get that having to go through lots of pages to get through the Visit logs is tedious, boring and uses data. So encourage Groundspeak to enhance the website's TB log display to do the same thing as the cache log display: keep doing CTRL-END to load more logs!
I have only a handful of TB's and they are all relatively new, so they have only been retreieved and dropped 3 or 4 times, but yet they have 20 pages of logs, so its almost impossible to see where it has actually been and who has had it.
If some people like the Visited TB feature and want to use it <or over-use it> thats fine, but I would like to have the capability to turn VISIT's OFF for my trackables, or an easy way to delete those log entries from my TB logs.
-
I'm relatively new to caching (450 finds) and have recently released a few trackables. I was excited to get some notifications that my trackables were moving, then when I went to see where the trackable was and where it had been I found pages and pages of "Took it to" or "Visited" logs, but only 3 or 4 actual "dropped" or "retrieved" logs...
Because of the way the GS interface works for logging a find its a one-click automatic action to log ALL the trackables in your possession as having "visited" every cache find you log, whether you are actually carrying the trackable to the cache or not.
I love to see my trackables moving, but to me, fake visits because of a one-click feature of the cache find logging tool is NOT "moving", I would like to see only logs of my trackables actually moving, from place to place, and from cacher to cacher, and it seems like the "Visited" entries make that almost impossible the way it is currently implemented.
-
1
-
.png)
.png)
How long is it reasonable to keep a TB in transit from one cache to the next?
in Trackables
Posted
Misery loves company! I'm glad to hear that I'm not the only one frustrated by people holding TB's for months at a time an logging pages and pages of Visit logs! Between that and phony "Discovered" logs from people distributing lists of TB ID numbers and cachers who pick up TB's and never drop them or even log them again, I have really lost hope and interest in TB's.
I've even put notes in all my TB's asking people to NOT log Visits and to promptly move TB's along, it doesn't help.
I've messaged cachers asking them to move along TB's and not log Visits, and it usually just results in a "Mind Your Own Business" response or worse...
I think TB's are a great fun idea that has been destroyed by people laziness or selfishness...