[boulder.pm] Stein, "Network Programming With Perl"

Justin Simoni jsimoni at totalsite.com
Wed Jan 10 12:55:49 CST 2001


> I'm Walter, I'm 42, and I have less hair every day.  ;^)

hello Walter, actualy, now my hair is green, and kinda dirty  blind, I have
to redie it, or people will start to think I'm a perl street bum and give me
change.Which I'll take anyways,

> you undertook this project for a reason, and knowing that might help
> folks understand the differences between Mojo Mail and major(domo|cool)
> or Mailman.  Do you have a FAQ list or something (I didn't see one).

i was an owner of a few majordomo lists, and not a happy person about it.
Every time a mailing would get out, I (as the owner) would be deluged with
bounced, arrgh.  Also, the site was a youth-oriented skateboard site, so the
visitors would have trouble with the directions. I'm a very visual person,
and majordomos email interface was somewhat clunky,

subscribe [password] <thislist> "email address"

i never got the hang of it, and being the lazy person I am, wrote my own
little MLM :) Mojo is more oriented to regular people, its all web-based,
all visual, 'Mac-Like' in its simplicity, but roaring with features (now
anyways). The 2.4 release is a major overhaul of its archiving system,
(which, is still very simple)  and includes full smtp support.

Lists take a minute to make, you give the password, enter a List Name, a
list owner e-mail address, and the list is made! plunk in all your favorite
friends and *click* you have a list. Mojo takes care of automatically
message archiving, keeping the list clean, what have you.

But mostly, mojo was a change for me to experiment with Perl and learn it.
If you go through the source code of each release, you'll see what I
probably learned in that time period, (the flavor of the week) early
versions showed that I could create  a somewhat large script without strict
:) the next version showed I could rewrite a totally fumbled script using
strict() , another version might show how I learned how to create modules,
link them up, use them with 'use' 'require'., make OO modules, Use CGI html
shortcuts, yadda yadda yadda.

The design of the program, the html you'll actually see, is just as
important as the junk that somehow makes it work, How do I make an
incredibly difficult task easy for the user? example? How do I send my
message to 50,000 people using the Bulkmail module as the sender. Well, in
your contro panel, go to sending options and click 'Use SMTP' all the
functions are like that.  What's the point of a program if you can't use it?

I released it as open source, just to share, and after a while, I got a
following, One time I was testing a beta and screwed up a /few/ test
sendings, what happened? My entire announce list of about 350 got about 10
weird test messages that didn't amke any sense. Did everyone unsubscribe
from the list? NO! I worte an apology and about a quarter of the list wrote
back saying 'no problem happens all the time with me'

Also, I didn't know about Majordomo2, but it still looks like a pain to
install, and way to complex for me. Mailman looks very elegant,  really like
the user page for every susbscriber.

and finally, I heard it got the chicks, anyone have luck with that?

I still see myself as not a beginning Perl hacker, but one rung up, there's
probably code in there that anyone else on this list will wince at. its all
a learning experiance.

justin 



 







> 
> I'm looking at your page on features, and it looks pretty nice, but tell
> me:  you undertook this project for a reason, and knowing that might help
> folks understand the differences between Mojo Mail and major(domo|cool)
> or Mailman.  Do you have a FAQ list or something (I didn't see one).
> 
> And a general announcement regarding the Stein book:  since I posted
> about it last night, I'm waiting 24 hours to give everyone, no matter
> what their weird hours may be, a chance for Fame and Fortune (well, a
> free book at least).
> 
> Walter
> 
> 




More information about the Boulder-pm mailing list