I see a definite problem developing here. A few years back when the Smew showed up on the Columbia River, it was reported inboth western and eastern Oregon field notes in Oregon Birds. If we can’t decide where the boundary is for those geographical areas, how on earth are we going to do so for some spot in the blue Pacific? This whole thing is all too funny. I’m with Patterson on this one. Lots of lists, few which conform to ABA rules. Darrel Sent from Windows Mail From: Joel Geier Sent: February 5, 2014 8:16 AM To: Oregon Birders OnLine Subject: [obol] Re: Wherefore art thou, oh albatross? I also see a HUGE opportunity to establish a new listing fiefdom in the Benthic-Cascadia Unclaimed Zone (or just B-CUZ, for short). Herewith I announce the formation of the brand-new B-CUZ Bird Records Committee which will be devoted entirely to review of bird reports from the unclaimed wedge of the northeastern Pacific Ocean. Send your reports from B-CUZ to the address below. The Committee will review these during our periodic meeting, to be held in the B-CUZ whenever the water gets warm enough for swimming. Please do not send long written descriptions, as they are difficult to read while treading water. Similarly, do not send digital images as it's hard to view these on a laptop while keeping it out of the water. Photos will just get soggy. In other words, please just tell us how many "friends" you have on Facebook, and sign our standard waiver in which you promise to NEVER, ever send your report to any other Bird Record Committee that tries to claim this wedge of saltwater. Please include 20 krugerrands with your report to cover processing (sorry, we cannot accept paper currency, checks, or bitcoin, for reasons which should be obvious). Here is the address for those reports: Benthic-Cascadia Bird Records Committee Attn: Sexton-in-Chief Shearwater Bight Offshore of the Isle of Man OBOL archives: www.freelists.org/archive/obol Manage your account or unsubscribe: //www.freelists.org/list/obol Contact moderators: obol-moderators@xxxxxxxxxxxxx