AT&T @home questions...

[Matt Graham]

So everyone's favorite evil phone company is now offering cable-modem
service to the area where I live. I know from scuttlebutt on Usenet and
the thread started at
http://www.egr.msu.edu/archives/public/linux-user/2001-June/004173.html
that people can get the service to work under Linux reasonably easily. I
have perused the company's website, checked out their amazingly
content-free FAQ, and their amazingly weasel-worded TOS. (Say, what is
the legalese for "All your soul are belong to us"?)
 
Anyway, the TOS does not say "You are not allowed to run an
HTTP/FTP/SMTP/ SSH login server". Am I correct in assuming that @home
subscribers are allowed to run these services? (I know a couple of
things about securing a machine, and will not run open relays,
globally-accessible NFS/SMB, telnetd, or really old versions of BIND
here.) The 128kbps upstream cap blows goats, but it's about 3x faster
than what I have now and I suppose I can live with it.  (Idiots.
Freenet/OpenNap/Gnutella show that people want to share stuff; even if
they threw out a bone like "Upstream: 128kbps to the Net at large,
768kbps to other @home users", they'd get more Clued and more k1dd13s
jumping on their bandwagon.)
 
Any comments/advice/howls of pain from those currently using @home from
AT&T are appreciated. 

-- 
Matt G / Dances With Crows
There is no Darkness in Eternity/But only Light too dim for us to see
"I backed up my brain to tape, but tar says the tape contains no data...."