Yahoo Groups archive

MOTM

Index last updated: 2026-04-28 23:35 UTC

Message

RE: [motm] What's the deal with the list

2003-02-06 by Alan Wagner

Robert,
I very surprised that you had this reaction... I joined the list a little
over a year ago (before I even had my first order) and have been met with a
warm welcome. The people on this list have been gracious and supportive of
all my stupid questions! Please don't let the foolishness of one individual
spoil the benefits of being on this list!

Al

-----Original Message-----
From: Robert van der Kamp (by way of Robert van der Kamp <robnet@...>)
[mailto:robnet@...]
Sent: Thursday, February 06, 2003 2:23 AM
To: motm@yahoogroups.com
Subject: Re: [motm] What's the deal with the list

On Thursday 06 February 2003 04:43, Paul Schreiber wrote:
> The list is PRIVATE, by invatation only. This prevents it
> from turning into a 3-ring circus.
>
> When an order is placed or shipped, I send out that info
> in a private email.

When I decided to get involved with MOTM, about a year ago,
I found the list on the Yahoo groups and became member
using the standard yahoo interface. No problem at all.

This probably explains some hostile reactions to my
 presence on the list, especially when I explained I still
 don't have any MOTM module (I have 11 on order now, so you
 can sit down again ;). People assumed I'm a troll for some
 reason, while I'm being polite and all, and just wanted to
 learn about MOTM before I buy. And for several reasons
 that first order took longer than expected.

I even got a private email a couple of month ago from a
member telling me to f**k off, just out of the blue. He
apologized after I explained the situation. Looks like the
formula is this:

        list member without MOTM stuff == troll.

So why is this list closed like a fortress?

- Robert




Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.