On Tue, 2006-05-23 at 17:53 +0200, houghi wrote:
> On Tue, May 23, 2006 at 11:14:54AM -0400, Kenneth Schneider wrote:
> > I have been on suse-linux-e for quite some time (I joined sometime in
> > 1999) and it is not as bad as you make it out to be. I see maybe 1 html
> > email a week. 
> 
> I don't recall the numbers I saw. It was the general feeling after lurking
> that I disliked it. This is how _I_ feel about it. In no way do I want to
> say that that is what other people think, should think or experience.
> 
> <snip>
> > This use to be the case until a
> > certain SuSE employee left the company. Perhaps that is all that is
> > needed again, a list moderator. Not in the sense that that person manage
> > every email that is posted but someone that can step in and put a halt
> > to certain threads when they get out of hand, OT messages and messages
> > that belong to another list.
> 
> Step one is to block HTML and binaries, I think. As long as you have a
> reply that explains it, there should not really be a problem.
> 
> > Top posting is a huge issue because there
> > is no one in charge to put a stop to it. The users, such as myself, try
> > to curtail its use but in the end we have no authority to stop it and
> > the top posters know that we do not.
> 
> I can imagine that the SUSE people don't want to tell their users off.

They would -not- be telling their users off just setting up some ground
rules. Kind of what you do here when people top post and post technical
questions. If there was someone in charge of how/what messages were
posted people would be more inclined to follow the requests.

> Many people would feel insulted and that is something you do not want to
> happen if you are a company.

No, they would more feel ashamed that they were reminded of the
procedures requested for posting to the list.

-- 
Ken Schneider
UNIX  since 1989, linux since 1994, SuSE  since 1998


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to