Found a cache archived five months ago

[+.Oystercacher]

Hi.New here and would like a few thoughts on this one please.

 

Went to grab a couple of local caches that I had on my GPS.At one of them I noticed the log was last signed April 2014.Got home to log my visit but cache wasn't showing on map so found it via the CO's profile.

 

The log was something like this.

April 2014 Found

May 2014 DNF

Aug 2014 DNF

Sept 2014 DNF

Jan 2015 CO checked on this today cache has gone time to archive it.

 

As you can see it's a cache that doesn't get too many visits but its on the way to another of the CO's caches.Obviously I want to log the cache so I'm thinking shall I log it but that'll make the owner look a bit stupid as the cache was tied to a tree and the co-ords were spot on (thats if they actually did go and check it had gone.From their profile I believe they would have done) Or PM the owner and tell them its actually still there.Owner has quite a few caches locally.

 

Just wondered what others would do or the etiquette for such a situation.

 

PS.I know I should have updated my GPS.

[+on4bam]

PS.I know I should have updated my GPS.

 

Exactly!

 

Before going on a caching trip you should update the caches of the area. That way, going out to find an archived cache wouldn't happen.

[+Dread_Pirate_Bruce]

If you found it and signed the log, log it as a find. However, make t clear in your log that you did find it and it is where it was supposed to be.

 

The CO may delete it, in which case a complaint to the local reviewer is in order. Archiving a cache and not removing it is to leave geo-trash.

[+Ben0w]

Beware: a cache could be archived on geocaching.com but maybe active on another listing site!

 

Mail the owner. Ask him politely to unarchive the listing (however, I think after more than three months this isn't possible any more), alternatively to tell you which other listing sites the cache belongs to or - if it's really inactive - to get his geo litter collected ASAP.

 

If you happen to get there again, you could do the "trash out" part, if appropriate.

 

Logging that as a found it is technically possible. Ethically, the cache is out of game, but if you honestly searched for it based on outdated information and signed the logbook, I don't see that as foul play. Your choice.

[+Bear and Ragged]

Sign the log? Log it on line.

 

Offer to tell the CO where it is, if they want to know.

(Just because you think its at the 'correct' coordinates, doesn't mean it is! . Could be someone moved it from where the CO placed it, to where they thought it should be..)

[Keystone]

The CO may delete it, in which case a complaint to the local reviewer is in order.

Community Volunteer Reviewers do NOT get involved in logging disputes. Please review this Help Center article.

[Pup Patrol]

Hi.New here and would like a few thoughts on this one please.

 

Went to grab a couple of local caches that I had on my GPS.At one of them I noticed the log was last signed April 2014.Got home to log my visit but cache wasn't showing on map so found it via the CO's profile.

 

The log was something like this.

April 2014 Found

May 2014 DNF

Aug 2014 DNF

Sept 2014 DNF

Jan 2015 CO checked on this today cache has gone time to archive it.

 

As you can see it's a cache that doesn't get too many visits but its on the way to another of the CO's caches.Obviously I want to log the cache so I'm thinking shall I log it but that'll make the owner look a bit stupid as the cache was tied to a tree and the co-ords were spot on (thats if they actually did go and check it had gone.From their profile I believe they would have done) Or PM the owner and tell them its actually still there.Owner has quite a few caches locally.

 

Just wondered what others would do or the etiquette for such a situation.

 

PS.I know I should have updated my GPS.

 

You found the cache and signed the log in it? The cache page is not locked?

 

Log it as "found" online, and tell the story of how you found it.

 

Lots of people have logged archived caches. There's nothing to say that you can't do so.

 

If the owner is interested, and the cache is not in violation of any Guidelines, then they can get in touch with Groundspeak about the possibility of re-activating the listing.

 

B.

[Pup Patrol]

Was it this one?

 

Blue Arrow

 

http://coord.info/GC20A9B

 

 

B.

[+narcissa]

Just log it. Mention in the note that it was in your GPS and you didn't realize it was archived, but it's still in place. Don't react to drama that hasn't happened. People find archived caches all the time.

Edited June 21, 2015 by narcissa

[+Mudfrog]

Just log it. Mention in the note that it was in your GPS and you didn't realize it was archived, but it's still in place. Don't react to drama that hasn't happened. People find archived caches all the time.

 

Exactly!

 

You found it, you signed the logsheet at the cache, and you log it online. No further action is necessary, at least at this time.

[+captnemo]

Just log it. Mention in the note that it was in your GPS and you didn't realize it was archived, but it's still in place. Don't react to drama that hasn't happened. People find archived caches all the time.

 

Exactly!

 

You found it, you signed the logsheet at the cache, and you log it online. No further action is necessary, at least at this time.

+1

[+.Oystercacher]

PS.I know I should have updated my GPS.

 

Exactly!

 

Before going on a caching trip you should update the caches of the area. That way, going out to find an archived cache wouldn't happen.

That's why I added the PS as I knew that would be mentioned I'm just a bit unorganised.One thing it's taught me to keep updated as I might be missing out on new caches as well as wasting time with archived stuff...this time I got lucky

 

Just as a side note.Found a cache a couple of months ago on a Monday,went to log it on the Wednesday and found it had been archived on the Tuesday.

[+.Oystercacher]

Was it this one?

 

Blue Arrow

 

http://coord.info/GC20A9B

 

 

B.

I could say no but the evidence says otherwise well done Mr Holmes

[+.Oystercacher]

Just log it. Mention in the note that it was in your GPS and you didn't realize it was archived, but it's still in place. Don't react to drama that hasn't happened. People find archived caches all the time.

 

Exactly!

 

You found it, you signed the logsheet at the cache, and you log it online. No further action is necessary, at least at this time.

+1

Thanks for the replies I've let the CO know and will log it later.

[+on4bam]

That's why I added the PS as I knew that would be mentioned I'm just a bit unorganised.One thing it's taught me to keep updated as I might be missing out on new caches as well as wasting time with archived stuff...this time I got lucky

 

It could have been different. Imagine starting a series and DNF-ing all of them because they were archived weeks before.

On some cachetrips I sometimes even refresh my selection for the day just before we leave home just in case there are issues. I wouldn't dream to leave home with even 1 week old listings.

[+GrateBear]

Interesting discussion, some of which I question. The reason being because of the sometimes angst I see over logging archived virtual caches. Many of those that have been archived are still in place, yet if people start logging them, they get locked. Hmmmm............

[+Ben0w]

1. If archived (on any listing service), the cache is out of the game.

2. The box turned into geo litter and should have been taken away by the cache owner, so no find is possible.

 

However, there is a grey area. If #2 hasn't happened (yet or because the CO doesn't know where it is) and the finder honestly isn't aware of the archiving, then I'd consider it a legal find. Just logging archived virtuals because no physical log is needed is foul play in my book...doesn't hurt anyone, but makes me laugh (again) about the significance of "found it" statistics.

 

If #2 doesn't happen for a long time, it's bad. There may be a bunch of reasons. Then, local geocachers should offer the CO to help getting the trash out or take action in a reasonable way. Geo litter shouldn't exist.

[knowschad]

1. If archived (on any listing service), the cache is out of the game.

2. The box turned into geo litter and should have been taken away by the cache owner, so no find is possible.

 

However, there is a grey area. If #2 hasn't happened (yet or because the CO doesn't know where it is) and the finder honestly isn't aware of the archiving, then I'd consider it a legal find. Just logging archived virtuals because no physical log is needed is foul play in my book...doesn't hurt anyone, but makes me laugh (again) about the significance of "found it" statistics.

 

If #2 doesn't happen for a long time, it's bad. There may be a bunch of reasons. Then, local geocachers should offer the CO to help getting the trash out or take action in a reasonable way. Geo litter shouldn't exist.

 

3. The archived cache is abandoned by the cache owner (shame shame!) but a geocacher, for whatever reason, goes out, finds it, and removes the geolitter, a find is perfectly acceptable in my book.

[+Ben0w]

1. If archived (on any listing service), the cache is out of the game.

2. The box turned into geo litter and should have been taken away by the cache owner, so no find is possible.

 

However, there is a grey area. If #2 hasn't happened (yet or because the CO doesn't know where it is) and the finder honestly isn't aware of the archiving, then I'd consider it a legal find. Just logging archived virtuals because no physical log is needed is foul play in my book...doesn't hurt anyone, but makes me laugh (again) about the significance of "found it" statistics.

 

If #2 doesn't happen for a long time, it's bad. There may be a bunch of reasons. Then, local geocachers should offer the CO to help getting the trash out or take action in a reasonable way. Geo litter shouldn't exist.

 

3. The archived cache is abandoned by the cache owner (shame shame!) but a geocacher, for whatever reason, goes out, finds it, and removes the geolitter, a find is perfectly acceptable in my book.

Yes. But there are some practical problems with that:

• why does the cacher search for the archived cache in the first place? If he knows it's archived, he should respect that. If not, well, then he doesn't even know, it's archived (D'oh!).

• if he didn't know that it's archived, how should he determine it in the field? Internet access isn't everywhere.

• even if he somehow learns on scene, it's archived: how does he know it's not active on another listing platform? Research? Internet access isn't everywhere. Better ask the owner! But that's not always possible on an outdoor trip.

• If he could mail the owner what's up with the cache and what to do, most probably, the reply will not be in time the cacher is still at the hide...

 

Just taking a cache without respecting CO's possession rights (and duties) because you think it's geo litter is not correct either. Determining this all in the field is very difficult.

[Pup Patrol]

Was it this one?

 

Blue Arrow

 

http://coord.info/GC20A9B

 

 

B.

I could say no but the evidence says otherwise well done Mr Holmes

 

Ms. Holmes, actually.

 

You left enough clues that even Watson could have found it.

 

The reason I asked is because there is another cache, by the same hider, .3 miles away.

 

Now that we know you found it "months ago", I think logging the find is inconsequential now.

 

But I see you've contacted the CO, so whatever he/she says is the main thing.

 

The cache probably did go missing after you found it. If you had found it after the archival note, then that would change the situation.

 

B.

[+colleda]

It's all about the numbers. LOG IT!!

[+bflentje]

PS.I know I should have updated my GPS.

 

Exactly!

 

Before going on a caching trip you should update the caches of the area. That way, going out to find an archived cache wouldn't happen.

 

Now that some have managed set you straight so long as your name is on the correct log for the archived cache, log it as a find. As for picking up the geo-trash, it's debatable.. never know if it's listed on another site or if it doubles as a true letterbox.

[+noncentric]

Along the topic of logging archived caches. Recently saw this archived cache get logged by hundreds of folks after it was archived, but presumably the CO didn't remove the cache.

 

Cache was archived May 24th, 2012

It was found a few months later, then again the following year, then again this past weekend. Finds usually corresponded to a local mega event that happens in the third week of August. It wasn't found in 2014.

 

This past weekend had over one hundred finds. This weekend was my first time caching when a lot of other cachers are in the area. I learned that once one person starts signing a log, then a line quickly forms and subsequent cachers don't even need their GPSr's to make the 'find'. That must've happened with this cache, but it still seems odd that someone would've had this in their GPSr after being archived for so long.

 

Will be interesting to see how many finds it gets next year.

[+L0ne.R]

PS.I know I should have updated my GPS.

 

Exactly!

 

Before going on a caching trip you should update the caches of the area. That way, going out to find an archived cache wouldn't happen.

 

Now that some have managed set you straight so long as your name is on the correct log for the archived cache, log it as a find. As for picking up the geo-trash, it's debatable.. never know if it's listed on another site or if it doubles as a true letterbox.

 

The chances it's listed on another site is miniscule. Hopefully the logbook would include information about where the cache is listed.

 

Also, if it's a letterbox, check the logbook - it should have signature stamps inside. It'll look something like this:

 

 

[+JL_HSTRE]

If you found then log it, archived or not. CO not finding their own cache is not unheard of. Explain the situation in your log. Perhaps include a politely worded suggestion that the cache be unarchived or the container removed.

[+narcissa]

I don't know why some people are so severe about this. The cache belongs to the owner. Just because the listing is archived doesn't mean the cache owner doesn't have other plans for it. People really need to get over this silly notion that geocaching only exists on one website and everything else is litter.

[+NeverSummer]

1. If archived (on any listing service), the cache is out of the game.

2. The box turned into geo litter and should have been taken away by the cache owner, so no find is possible.

 

However, there is a grey area. If #2 hasn't happened (yet or because the CO doesn't know where it is) and the finder honestly isn't aware of the archiving, then I'd consider it a legal find. Just logging archived virtuals because no physical log is needed is foul play in my book...doesn't hurt anyone, but makes me laugh (again) about the significance of "found it" statistics.

 

If #2 doesn't happen for a long time, it's bad. There may be a bunch of reasons. Then, local geocachers should offer the CO to help getting the trash out or take action in a reasonable way. Geo litter shouldn't exist.

 

3. The archived cache is abandoned by the cache owner (shame shame!) but a geocacher, for whatever reason, goes out, finds it, and removes the geolitter, a find is perfectly acceptable in my book.

Yes. But there are some practical problems with that:

• why does the cacher search for the archived cache in the first place? If he knows it's archived, he should respect that. If not, well, then he doesn't even know, it's archived (D'oh!).

• if he didn't know that it's archived, how should he determine it in the field? Internet access isn't everywhere.

• even if he somehow learns on scene, it's archived: how does he know it's not active on another listing platform? Research? Internet access isn't everywhere. Better ask the owner! But that's not always possible on an outdoor trip.

• If he could mail the owner what's up with the cache and what to do, most probably, the reply will not be in time the cacher is still at the hide...

 

Just taking a cache without respecting CO's possession rights (and duties) because you think it's geo litter is not correct either. Determining this all in the field is very difficult.

Wait... "he should respect that"? Respect what, exactly? An archived cache does not mean anything other than that it should not be there anymore, and that it can't be searched in active caches. If an owner wants their archived cache to be "respected"by not getting any more "Found It!" logs, then they should assure that the cache is gone and logbook can't be signed.

 

I've found many caches that were left as geotrash by an owner (on purpose, by accident...doesn't matter), and logged the find. If the owner was no longer playing, or made it clear they thought it was gone, I've trashed or recycled containers.

 

I do agree that asking if the cache is cross-posted on another service is a good idea before walking off with an archived cache. There's not much of that to worry about up here in Alaska, but I know that it was an emerging issue in Minnesota, Oregon, and North Carolina (and likely in Georgia, where I'm moving to soon).

[+J Grouchy]

I do agree that asking if the cache is cross-posted on another service is a good idea before walking off with an archived cache. There's not much of that to worry about up here in Alaska, but I know that it was an emerging issue in Minnesota, Oregon, and North Carolina (and likely in Georgia, where I'm moving to soon).

 

The other listing sites are really not 'a thing' in my area (metro Atlanta)...so I'm not sure what you mean by that. Around here, the biggest issue seems to be the primary reviewer who actually does his job and clears out abandoned caches (and the folks who don't like when he does that).

 

So what part of GA are you moving to?

[+NeverSummer]

I do agree that asking if the cache is cross-posted on another service is a good idea before walking off with an archived cache. There's not much of that to worry about up here in Alaska, but I know that it was an emerging issue in Minnesota, Oregon, and North Carolina (and likely in Georgia, where I'm moving to soon).

 

The other listing sites are really not 'a thing' in my area (metro Atlanta)...so I'm not sure what you mean by that. Around here, the biggest issue seems to be the primary reviewer who actually does his job and clears out abandoned caches (and the folks who don't like when he does that).

 

So what part of GA are you moving to?

I meant that there might be cross-posted GPS-related gamepieces in Georgia, unlike most Geocaches here in Alaska. I was stating the places where I have lived, and the trends I've seen with cross-posting. None of the states or areas I lived in had an epidemic of cross-posted caches, so I'd really say it isn't a worry overall when finding an archived Geocaching.com Geocache. But, still a good idea to check with an owner (if they respond?) and act accordingly.

 

Personally, I'd still remove the geotrash, as the cache was listed on Geocaching.com and not removed from its location--and the owner could/should state on the cache page webpage, via "Archived" log on Geocaching.com that it is cross-posted so people might know in the future what it is they are finding, etc.

 

I'm headed to the Savannah area.

 

Edited to clarify

Edited August 19, 2015 by NeverSummer

[+hzoi]

I do agree that asking if the cache is cross-posted on another service is a good idea before walking off with an archived cache. There's not much of that to worry about up here in Alaska, but I know that it was an emerging issue in Minnesota, Oregon, and North Carolina (and likely in Georgia, where I'm moving to soon).

 

The other listing sites are really not 'a thing' in my area (metro Atlanta)...so I'm not sure what you mean by that. Around here, the biggest issue seems to be the primary reviewer who actually does his job and clears out abandoned caches (and the folks who don't like when he does that).

 

So what part of GA are you moving to?

I meant that there might be cross-posted GPS-related gamepieces in Georgia, unlike most Geocaches here in Alaska. I was stating the places where I have lived, and the trends I've seen with cross-posting. None of the states or areas I lived in had an epidemic of cross-posted caches, so I'd really say it isn't a worry overall when finding an archived Geocaching.com Geocache. But, still a good idea to check with an owner (if they respond?) and act accordingly.

 

Personally, I'd still remove the geotrash, as the cache was listed on Geocaching.com and not removed from its location--and the owner could/should state on the cache page on Geocaching.com that it is cross-posted so people might know in the future what it is they are finding, etc.

 

I'm headed to the Savannah area.

Enjoy. Savannah is a great area.

 

Does that mean you'll be NeverWinter soon?

[+on4bam]

It surprises me that people would have caches on their GPS for more than 5 months without getting updated data.

 

On the other hand, I see archived caches being logged (a week or less after archiving) where there's a great possibility that it was armchair logging (as there were a lot of DNF/NM before archiving. Easy points if the CO is no longer active or cache disappeared (with log).

[+narcissa]

It surprises me that people would have caches on their GPS for more than 5 months without getting updated data.

 

On the other hand, I see archived caches being logged (a week or less after archiving) where there's a great possibility that it was armchair logging (as there were a lot of DNF/NM before archiving. Easy points if the CO is no longer active or cache disappeared (with log).

 

It is more likely that someone in the group said "Hey, there used to be a cache in this tree..."

[+NeverSummer]

Enjoy. Savannah is a great area.

 

Does that mean you'll be NeverWinter soon?

Believe me, I thought about my cache handle and the new locale! Moving around from MN to OR to MN to AK since starting with geocaching certainly has kept me in cooler climes!

[Keystone]

I meant that there might be cross-posted GPS-related gamepieces in Georgia, unlike most Geocaches here in Alaska. I was stating the places where I have lived, and the trends I've seen with cross-posting. None of the states or areas I lived in had an epidemic of cross-posted caches, so I'd really say it isn't a worry overall when finding an archived Geocaching.com Geocache. But, still a good idea to check with an owner (if they respond?) and act accordingly.

 

Personally, I'd still remove the geotrash, as the cache was listed on Geocaching.com and not removed from its location--and the owner could/should state on the cache page on Geocaching.com that it is cross-posted so people might know in the future what it is they are finding, etc.

1. Stating that your cache is cross-listed on SecondaryCachingSite.com is bad form; most reviewers do not allow such statements as they are promotional.

 

2. There's one less "alternative listing site" than there was yesterday, so the concern is lessened by a significant degree today.

[+NeverSummer]

I meant that there might be cross-posted GPS-related gamepieces in Georgia, unlike most Geocaches here in Alaska. I was stating the places where I have lived, and the trends I've seen with cross-posting. None of the states or areas I lived in had an epidemic of cross-posted caches, so I'd really say it isn't a worry overall when finding an archived Geocaching.com Geocache. But, still a good idea to check with an owner (if they respond?) and act accordingly.

 

Personally, I'd still remove the geotrash, as the cache was listed on Geocaching.com and not removed from its location--and the owner could/should state on the cache page on Geocaching.com that it is cross-posted so people might know in the future what it is they are finding, etc.

1. Stating that your cache is cross-listed on SecondaryCachingSite.com is bad form; most reviewers do not allow such statements as they are promotional.

 

2. There's one less "alternative listing site" than there was yesterday, so the concern is lessened by a significant degree today.

I didn't mean in the listing description. I meant perhaps adding it to their "Archived" log, if it was in fact the owner who archived the listing.

 

It's just nice to have owners who are clear, responsible, and honest. Just saying...

 

Edited to clarify.

Edited August 19, 2015 by NeverSummer

[+niraD]

2. There's one less "alternative listing site" than there was yesterday, so the concern is lessened by a significant degree today.

That's good to know. Thanks!

[+GeoBain]

1. Stating that your cache is cross-listed on SecondaryCachingSite.com is bad form; most reviewers do not allow such statements as they are promotional.

 

What would happen? Would they archive the archived cache?

[+TriciaG]

1. Stating that your cache is cross-listed on SecondaryCachingSite.com is bad form; most reviewers do not allow such statements as they are promotional.

 

What would happen? Would they archive the archived cache?

They could require you to delete the statement or delete it themselves.

 

What options to reviewers have when ANY guideline is violated in a cache listing?

[+NeverSummer]

1. Stating that your cache is cross-listed on SecondaryCachingSite.com is bad form; most reviewers do not allow such statements as they are promotional.

 

What would happen? Would they archive the archived cache?

They could require you to delete the statement or delete it themselves.

 

What options to reviewers have when ANY guideline is violated in a cache listing?

But what about saying, "Archiving this cache. It is still active as a cache on another website, so please do not remove if you find it after archival on this website. Thank you."?

 

Rare case, I'm sure, but what's the harm there?

 

Again, archive the archived cache? Delete a log which helps make it clear that the container still remains, even if it isn't part of Geocaching.com's Geocache listing service anymore?

[+NeverSummer]

The flip side of this case has been this, personally:

Archived cache. Someone logs a "Found it" a while after archival, saying they "...found it after it was archived...I still had it in my GPS...". Thing is, I know it was gone, because I removed it before they said they had found it. Emails to the owner to clarify went unanswered. Log deleted.

 

So it all comes down to this: Are owners maintaining their cache listing and location of their hide? Not 100% compliant, we could all agree. If your cache is going to be archived, remove the cache. Done deal. That might mean it "goes missing" and someone finds it long after. Ok, ask that finder about the cache, and the owner goes to remove it after learning it's missing.

 

Or, they can re-submit a listing for the container, or ask for it to be enabled.

 

Bottom line is that owners need to take care of their listings and caches.

[+on4bam]

I know of a cacher who removed (archived) all his caches from gc because of a disagreement with gc. All his caches are still active on opencaching so you could find these archived caches and log them (I guess logs would be deleted, don't know). I see no reason why this CO would need to remove his caches, they are still active, only not here.

 

Why not "lock" a listing (some time) after a cache is archived so these "founds" don't get logged anymore?

[+NYPaddleCacher]

 

I'm headed to the Savannah area.

 

Tybee Island?

 

I've enjoyed the geocaching that I've done in the area. Get a kayak. There is some really wonderful kayaking in that area, including a spot called the triangle that some consider to be the best kayak surfing area in the country.

 

 

[+TriciaG]

But what about saying, "Archiving this cache. It is still active as a cache on another website, so please do not remove if you find it after archival on this website. Thank you."?

 

Rare case, I'm sure, but what's the harm there?

 

Again, archive the archived cache? Delete a log which helps make it clear that the container still remains, even if it isn't part of Geocaching.com's Geocache listing service anymore?

I'm perfectly happy with that log. I was just answering GeoBain's question about what the reviewer could do if a CO posted something against the commercial promotion guidelines.

 

The flip side of this case has been this, personally:

Archived cache. Someone logs a "Found it" a while after archival, saying they "...found it after it was archived...I still had it in my GPS...". Thing is, I know it was gone, because I removed it before they said they had found it. Emails to the owner to clarify went unanswered. Log deleted.

 

So it all comes down to this: Are owners maintaining their cache listing and location of their hide? Not 100% compliant, we could all agree. If your cache is going to be archived, remove the cache. Done deal. That might mean it "goes missing" and someone finds it long after. Ok, ask that finder about the cache, and the owner goes to remove it after learning it's missing.

 

Or, they can re-submit a listing for the container, or ask for it to be enabled.

 

Bottom line is that owners need to take care of their listings and caches.

Yeah, that would annoy me. It'd be nice if a CO would say, "Archived and container removed." Then the CO could request (or GS could just automatically implement) that the listing be locked to further logs, perhaps after a reasonable time to let those who don't log online in a timely manner a chance to log their legitimate find.

 

[Edited to add response to another post]

Edited August 19, 2015 by TriciaG

[+TriciaG]

I know of a cacher who removed (archived) all his caches from gc because of a disagreement with gc. All his caches are still active on opencaching so you could find these archived caches and log them (I guess logs would be deleted, don't know). I see no reason why this CO would need to remove his caches, they are still active, only not here.

 

Why not "lock" a listing (some time) after a cache is archived so these "founds" don't get logged anymore?

Not a problem anymore, since opencaching went belly up a couple days ago.

[+narcissa]

I know of a cacher who removed (archived) all his caches from gc because of a disagreement with gc. All his caches are still active on opencaching so you could find these archived caches and log them (I guess logs would be deleted, don't know). I see no reason why this CO would need to remove his caches, they are still active, only not here.

 

Why not "lock" a listing (some time) after a cache is archived so these "founds" don't get logged anymore?

 

I can think of many geocaches that were placed by school groups, scouts, and other similar organizations who didn't understand the guidelines, and then swiftly archived due to serious issues. These caches tend to be placed for educational purposes for the group that is placing them, and adding them to Geocaching.com is just a fun side element. Once they get archived, they are still in use by those groups.

[+on4bam]

Not a problem anymore, since opencaching went belly up a couple days ago.

 

Too bad as I would have loved them (or any other) grow to a decent size. Monopolies are bad

On the other hand, it's only the .com that's go

[+niraD]

It'd be nice if a CO would say, "Archived and container removed." Then the CO could request (or GS could just automatically implement) that the listing be locked to further logs, perhaps after a reasonable time to let those who don't log online in a timely manner a chance to log their legitimate find.

In addition to those who are behind in their logging, there are also people who start out using a group/family account, or they start out just tagging along with a friend/relative who has an account. Later, they create a new personal account and post backdated logs for all the caches they've already found.

[+on4bam]

In addition to those who are behind in their logging, there are also people who start out using a group/family account, or they start out just tagging along with a friend/relative who has an account. Later, they create a new personal account and post backdated logs for all the caches they've already found.

 

Should be no problem to lock logging on newer dates than the archive date. Split accounts could then log the original date but the "I still had this ancient PQ on my GPS so I didn't know it was archived" cacher could not (unless they would fake the date but then 10's of "fake date loggers" would easily been spotted).

[+narcissa]

In addition to those who are behind in their logging, there are also people who start out using a group/family account, or they start out just tagging along with a friend/relative who has an account. Later, they create a new personal account and post backdated logs for all the caches they've already found.

 

Should be no problem to lock logging on newer dates than the archive date. Split accounts could then log the original date but the "I still had this ancient PQ on my GPS so I didn't know it was archived" cacher could not (unless they would fake the date but then 10's of "fake date loggers" would easily been spotted).

 

Why? What is the utility? If people are logging illegitimate finds on your archived caches, you can delete them.

[+NYPaddleCacher]

I know of a cacher who removed (archived) all his caches from gc because of a disagreement with gc. All his caches are still active on opencaching so you could find these archived caches and log them (I guess logs would be deleted, don't know). I see no reason why this CO would need to remove his caches, they are still active, only not here.

 

Why not "lock" a listing (some time) after a cache is archived so these "founds" don't get logged anymore?

Not a problem anymore, since opencaching went belly up a couple days ago.

 

Clarification: opencaching.com went belly up a couple of days ago but's all I can say about that.