Mike Harrison wrote:
> I can't see any way in which newsgroups would be better than Yahoo, and many downsides.

Con:
NO WAY TO STOP SPAMMERS FROM POSTING!
NO WAY TO STOP ADDRESS HARVESTING! user has to munge their address for safety.


So lets summarize:
=====================

Option 1. Mailman on MIT server.
Pro:
No adverts. No costs (Yet?).
Minimal transfer headache (export/import subscriber list).
Web interface for users to admin their own accounts.
Web interface for admin (passable).
Big (permanent) Archives??
Good ability to nuke/prevent spamming and address harvesting.

Con:
Admin tools are not great. Some admin time required.
Potential to be punted by MIT if BW use or costs become a problem.
Can the chosen MIT server handle the load? (mailman is not efficient).
========================

Option 2. Yahoogroup(s).
Pro:
Groups already exist. Pic one or the other or both.(piclist or piclistMIT)
Admin tools are good. Automanagement of common stuff (bounces etc).
Lots of extra's with yahoo (files, photos, chat, database, links, etc.)
Minimal transfer headache (expor/import subscriber list)
Good ability to nuke/prevent spamming and address harvesting.
Really FAT pipes. Yahoo hosts over a million lists.

Con:
Advert at bottom of every post.
May move to a charging model at some point (unlikely. Too many lists would leave).
No enforced topic tags. At posters discretion. User must do the filtering.
Limited archives (512MB or 30MB depending on creation date). We're 30MB.
==========================

Option 3. Multiple yahoo groups. One for each topic tag.
As above, but with one group for each topic tag.
Pro:
As above
filtered by subscription choice

Con:
As above
more addresses for user to remember/choose between. Subscription headache.
==========================

Option 4. Newsgroups
Pro:
Threads are handled automatically by news reader.
  (so sort email by subject).

Con:
NO WAY TO STOP SPAMMERS FROM POSTING!
NO WAY TO STOP ADDRESS HARVESTING! (user has to munge their address. Usually
   means a separate profile for news).
Not well propagated. Needs an official RFC (request for comments),
   CFV (call for vote) and 'makegroup' to get official sanction. Takes long time.
Takes much longer to propagate messages (daisy chain of distribution).
When a server goes down, everyone below looses posts, often permanently.
Many users cannot post or read newsgroups from work.
Not private. ANYONE, anywhere can read a post.
==============================

Option 5. Hosted by Microchip.
Pro:
Affiliation. Better responses from MC FAEs?

Cons:
Potential for censorship.
Cost and time for personnel at Microchip to set up.
Could go away on a whim (executive decision, cost vs. benefit, etc.
   Bandwidth isn't free).
Subscribers would possibly have to resubscribe themselves (depending on
software).
Unknown user interface, user tools and admin tools.
How long for MC to set up? Will MIT list still be around?
==============================

Option 6. Hosted on some other free list service
Pro:
Free
Web interface

Con:
Unknown lifetime. Business cannot run without an income stream.
  Advertising inevitable
Unknown capacity. 4GB/day required.

======================

Option 7. Paid hosting.
Pro:
Good service. Admins retain control.
No adverts.

Con:
Someone has to pay ALL the costs.
  Will subscription fees have to be charged?
Critical mass required if fees charged. No content, no subscribers.

=========================
The bandwidth load really IS 4GB a day.
200 posts/day * 2000 subs * 10k each is 4GB!!/day.
You need someone with a really FAT pipe to handle that load.

Feel free to add or refute points in this summary.

As always, you can voice your support for option 2 by subscribing
mailto:PIClistMIT-subscribe@yahoogroups.com

Is option 1 even available yet? James?

Robert

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu