Towertalk
[Top] [All Lists]

[TowerTalk] micro-reflectors

To: <towertalk@contesting.com>
Subject: [TowerTalk] micro-reflectors
From: antipode@ne.mediaone.net (antipode)
Date: Thu, 03 May 2001 18:34:06 -0400
I agree Bob.  Further it seems to me a micro-reflector is another
example of a solution looking for a problem so prevalent in today's
world of the home PC.  A central antenna reflector such as TowerTalk is
adequate and is rich in opinions and variety of topics.  For those posts
I'm not interested in, I simply use the delete key.  No big deal.  If
someone wants to write a new server program to do all kinds of neat
things they think are important, go right ahead.  If it's really all
that great, people will gravitate to it and it will survive.  If not,
well. . . you know.

Sounds like the KISS principle still applies.

73,
Bill Sievers
W5IQJ




 

Bob Otto wrote:
> 
> Hello Pete,
> 
> I agree with your comments.  I belong to several (6-8) reflectors, and
> there are a couple of conclusions I've drawn.
> 
> 1) TT is the most interesting to me because it covers such a wide
> variety of topics.
> 2)  Specialty lists seem to be very, very slow, and eventually die.
> 3)  By having a diverse bunch of topics....I actually learn much more
> and over the long haul, increase my pleasure in the hobby.
> 
> What would one rather do....belong to many lists to get answers,
> or have one good list??  I prefer one good list.
> 
> 73 from.......
> 
> Bob Otto
> N8NGA@one.net
> Cincinnati, Ohio
> 
> Time Written:
> 8:40:20 AM
> Attachments:
> <none>
> 
> **********************************************
> DXCC 10M         ** DX is !! **        WAS 10M
>        There is a very fine line between
>          "HOBBY" and "MENTAL ILLNESS"
> **********************************************
> When trouble arises and things look really bad,
> there is always one individual who perceives a
> solution and is willing to take command.
>       VERY OFTEN THAT PERSON IS CRAZY!
> **********************************************
> Thursday, May 03, 2001, 7:37:46 AM, you wrote:
> 
> PS> It seems to me that the history of ham reflectors demonstrates that
> PS> spinning off sub-topics is a hard thing to do.  Certain major subject
> PS> areas, like Towertalk, successfully spun off CQ-Contest.  Others, such as
> PS> antenna modeling (antennaware) did not, and even others that obviously 
> ring
> PS> a bell with a lot of people, like RFI, have been slow to take off.
> 
> PS> I would be wary of losing the critical mass of technically well-informed
> PS> participants if you subdivide too much more, and find it no problem to use
> PS> my delete key for threads that are not of interest.
> 
> PS> 73, Pete N4ZR
> PS> Contesting is!
> 
> PS> The World Contest Station Database
> PS> is waiting for your input at
> PS> http://www.qsl.net/n4zr
> 
> PS> List Sponsor:  ChampionRadio.com - Trylon self-supporting towers,
> PS> safety equipment, rigging gear, LOOS tension guages & more!
> PS> http://www.championradio.com
> 
> PS> -----
> PS> FAQ on WWW:               http://www.contesting.com/FAQ/towertalk
> PS> Submissions:              towertalk@contesting.com
> PS> Administrative requests:  towertalk-REQUEST@contesting.com
> PS> Problems:                 owner-towertalk@contesting.com
> 
> List Sponsor:  ChampionRadio.com - Trylon self-supporting towers,
> safety equipment, rigging gear, LOOS tension guages & more!
> http://www.championradio.com
> 
> -----
> FAQ on WWW:               http://www.contesting.com/FAQ/towertalk
> Submissions:              towertalk@contesting.com
> Administrative requests:  towertalk-REQUEST@contesting.com
> Problems:                 owner-towertalk@contesting.com

List Sponsor:  ChampionRadio.com - Trylon self-supporting towers,
safety equipment, rigging gear, LOOS tension guages & more!
http://www.championradio.com

-----
FAQ on WWW:               http://www.contesting.com/FAQ/towertalk
Submissions:              towertalk@contesting.com
Administrative requests:  towertalk-REQUEST@contesting.com
Problems:                 owner-towertalk@contesting.com


<Prev in Thread] Current Thread [Next in Thread>