Subject: Re: addresses in headers
Date: Nov 17 16:13:27 1994
From: Russell Rogers - rrogers


>From Russell Rogers, Seattle WA, rrogers at halcyon.com

I am an advocate in including your name and address (geographical as well as
your e-mail) in the body of your messages to tweeters. The reason for
this is that when you are talking about birds you need to know where a
persons point of view is coming from. A good case in point was my posting
from earlier this week. I forgot to include where a group of Brant that I
had seen this weekend was. Even though I should have remembered to
include the location on my posting by having my address there it could
have helped someone else figure out what the heck I was talking about.
Another example would be if someone sent out a posting asking if anyone
on tweeters has had an unusual number of Siskins at there feeders in the
past month. It would not be unusual for some replies to come back as "I
have had at least 50 an hour at mine." and that is it. Many, most,
perhaps all e-mail address don't give a clue as to your geographic
location. Mine is "rrogers at halcyon.com". This is a common problem on
nation wide listservers like Birdchat, where you have folks from all over
the country sending in addressless messages talking about what is coming
to there feeders. Even in a smaller listserver like tweeters this can be
a problem Washington is such a varied state. If someone posted that "on
my way to work to day I saw 150 Rosy Finches" with no geographic
reference, and a e-mail address like mine, you would have no clue as to
the importance of the posting. If that message was from someone from
Seattle, I would be in a fit to try and find out where this person
worked. If that person was working in Pullman, it would not be so
unusual.

It is for these reasons that I try to remember to put my full address on
posting that go out to tweeters. I will also try to remember to include
locations on my bird sightings. :)

Russell Rogers
4510 Glenn Way SW
Seattle, WA 98116
(206) 935-6280
rrogers at halcyon.com