It hath once been written:

>> JIC, assuming that this is all recognized by Tucows, then what is
>> the _real_ reason that this is being done? I am not trying to be
>> accusatory with this framing of the question, just making it clear
>> that this is where the logical steps must lead when taking these
>> considerations in mind.
>
>Cutting down the number of places one has to go to discuss our stuff is
>the real reason.

Agreed. And, this should include the number of places we, your customers,
have
to go, too.

We _all_ already use email. It is nice _now_ that we do not have to have
another
software package to deal with reading Tucows discussions, either.

Forcing this into another format does not make it easier for the large
majority
of your customers.

As well, you lose a great deal of participation, including just general
readership, by moving from a "opt-in push" to a "pull" format.

>What it's NOT about is editorial control. Consider that I'm given
>complete editorial autonomy over two blogs with the Tucows logo in
>their headings and under the tucows.com domain. No minders, no approval
>from the powers-that-be, just me.

I do not think really that this is much of a subject in the short term.

Of course, there is no denying that the possibility of exploitation does
increase with this change in the long term.

This possibility, and the eventuality that it has happened all too often in
the
online world with growing companies, is why steps such as this being made by
Tucows now are always to heavily resisted.

I for one am definitely not questioning the voracity of current Tucows
personnel
on this issue. But, none of us, including Tucows personnel, can vouch for the
veracity of all "personnel to come".

Maybe this is more of an issue of whether Tucows will state more clearly a
"company ethos" by not even allowing such systems that can allow such
editorial
control.

>What we *cannot* do is continue with a messy communications system
>where you have to use a mailing list for product X, a different mailing
>list for product Y and a forum system for product Z. Hence this
>migration plan.

Agreed. I think we all deal with this to one degree or another in our
businesses.

So, would not this be simpler to just use a capable list server package that
include threaded forums online?

I have yet to hear any reason why this option has not been the choice...

And, thank you Tucows for participating in this thread so actively. This is
definitely most appreciated by all of us, I believe.

Cheers!

================================================================
Steven G. Willis     [EMAIL PROTECTED]       866.224.3058
Deep Sky Technologies, Inc.          http://www.deepskytech.com/
http://www.badchickens.com/         http://www.store-secure.com/
AIM-iChat: dstisgwillis
================================================================
        Thankfully they created the word 'muffin'
     else I would be eating a cupcake for breakfast
================================================================

Reply via email to