[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] HELP
- Subject: RE: [cobalt-users] HELP
- From: baltimoremd@xxxxxxxxxxxxxxx
- Date: Tue Feb 6 22:33:03 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Tue, 6 Feb 2001, Tony wrote:
> +But, AFAIK, the control panel doesn't have such an option, does it?
> +
> +The very sarcastic point of my response was that I really don't believe in
> +results from wishlist@xxxxxxxxxx any more than the tooth fairy.
> +
> +Mind you, I am not a Cobalt expert, but based on my frustrations, those of
> +others and what seems to be a large collection of unfixed
> +problems/anomolies...wishlist@ might be better named pipedreams@
>
> Right.
>
> A good 70% of the list traffic could have been eliminated if Cobalt listened
> to customers and added these features by the Raq4. Seems the only thing that
> really escalates in each new generation of Raq product is the price. Instead
> in order to get these features we have to duct tape a wide variety of
> independent and opensource scripts to whatever Raq product is being used or
> create via command line with costly labor dollars.
The question might also be:
Why should Cobalt do anything to correct their errors/omissions if;
they perceive the typical customer will accept their offering,
they can charge for correcting their own mistakes,
they can void warranty if the owner has attempted to
modify/add to the Cobalt impolimentation
Using the reasons above:
Why would Cobalt post information about fixes to this list
So the question now is why does Cobalt have this list?
We are a large number of beta testers that actually paid to
enter the program.
The list allows us to ventilate
(years ago I worked in a very high pressure job with a
24 hour operation. The director insisted that every
"incident" was recorded in a log book that was reviewed
on a weekly basis. After a month on the job, I asked
why all the incidents that had been recorded had not
been addressed...and he told me "We don't even read the
log, but it does give your crew a place to ventilate.")
Personally, if I produced a product with as many long standing
problems as the Cobalt's, I'd make sure I never wore my name
badge outside of the building.
Thanks very much for the list....and you can also add the
problems with Majordomo
>
> No .htaccess/Directory Protection editing.
> No .procmailrc editor for REAL autoresponders
> No usable built-in Site Stats. (see scads of posts re Webalizer)
> No GUI file manager
> No GUI HTML creator (exists on Qube?)
> No GUI Mime editor
> No GUI Cron editor
> No SSH options
> No GUI control panel feature for MySql...the web's most popular db.
>
> Have I missed anything?
Perhaps others will add to the list...and I'd be happy to set up an
autoresponder(yea, I did it the hard way)
Thom
././././././././././././././././././././././././././././././././././././././
baltimoremd@xxxxxxxxxxxxxxx Thom LaCosta K3HRN Webmaster
http://www.baltimoremd.com/ Baltimore's Home Page
http://www.baltimorehon.com/ Home of the Baltimore Lexicon
http://www.zerobeat.net Home of The QRP Web Ring
and Drake Mail List Pages