Summer on the Hudson is one of my favorite area caches, bummer that it was a challenge to get listed.
I think sometimes there is a disconnect between a challenging cache and a problem cache. It is a drag when the admins assume at first that a challenging cache is a problem. But it's also fair to keep in mind that the admins have their own "admins" that they have to deal with, the kind that carry guns. And I think that as a caching community, as interesting and unthreatening and cache-worthy as we find bridges, we really have no true conception of how sensitive "admins with guns" treat even the most minor bridges. It's not even remotely similar to a cache placed on private property, or a park worker getting upset about permits, or a cache that requires somewhat dangerous rock climbing or a rappel line that many of us would be unqualified to hunt for. The worst that can happen authority-wise to an individual in any of those situations is, basically, nothing.
Contrast this with what happened on the Rainbow Bridge a couple of years ago. Most definitely not a major bridge, not a terrorism target, etc. etc. etc. It's just an insignificant little span in Nowhere, Idaho that nobody cares about.
http://www.fs.fed.us/r4/boise/emmett/el ... bridge.jpg
Long story short, when the authorities became aware of the cache, they completely freaked. They shut about 15 miles of the highway down for a few hours until they ultimately got everything sorted out, and wound up arresting the guy who placed it there for violating a bunch of laws that they claimed applied (he did avoid jail time in the end though). It's not geocaching-related, but the guys who placed the Cartoon Network advertising signs under Boston bridges were arrested afterwards as well, although I believe they also avoided jail.
The point isn't that these are sensible responses, or that the story are true parallel with anything that has happened in NYC geocaching. I am in complete agreement that these are totally ridiculous responses. The point is that admins have figured out that people not connected with the game who carry guns seem to care about bridges A LOT and that these folks are perfectly willing (eager?) to respond disproportionately - even for really stupid bridges that we all know nobody, but nobody, cares about. They treat these situations as humorlessly as they would someone waving a plastic gun near the presidential motorcade - which is to say with maximum response and zero risk. And so regardless of how challenging (or easy) a cache is, the admins want to steer clear of those problems. I can respect where they're coming from on that. I think this is why the caches in the subject line were retracted rather than archived - I've never seen another retraction before or since. Every other cache I've seen that later turned out to be in violation of guidelines has simply been archived, but in this case I think GC.com wants there to be as little evidence as possible that these were ever here. It's not that the admins think that caches on bridges are too dangerous. It simply shows how seriously they take the "admins with guns" opinion on the matter.
I also want challenging caches, and don't care a bit if there are listed caches I think are too dangerous for me to try. Frankly, if there aren't caches too hard for me, the scale is probably not calibrated correctly. My main concern is working to make sure that the admins don't treat every challenging or difficult cache like a problem cache (which can be a frustrating process), and to help other cachers understand the difference as well, to avoid all of the frustration and anger.
There are alternatives to the increasingly mainstream GC.com listing site as well. I don't think that caches that are considered big problems by the "admins with guns" are likely to be approved even by these alternatives, but I would venture to guess that caches that don't get approved by GC.com because they are too challenging would have a much easier time getting approved by these "old school" throwback sites. People should check out terracaching.com and navicache.com and see if there's something there that they like.
C-Ville, I'm intrigued by your cache ideas that have been shot down, I'm shooting you a private message now.