Domain: att.com
Stories and comments across the archive that link to att.com.
Comments · 1,491
-
Re:Hey, how about a few more links?!
-
Re:Another victim of the "Deathstar"...
Another victim of the "Deathstar"...
Err... Deathstar? I think you're confused. AT&T is the "Deathstar". See what I mean? -
Perl trying to outgrow its niche
Let's face it, perl is absolutely great for its original intention - fast, easy, write-and-forget scripting. But as I see the plans for Perl 6 unfold, one thought comes to my mind - Yuck. The language they propose is bloated and convoluted beyond words; it's clearly evident that Wall and his fellow "designers" are struggling vainly to make Perl "grow up" -- something that it has absolutely no need to do. There are other languages out there to fill the other niches; languages which try to do everything doom themselves to failure. Ambition kills.
-
Re:Qt/Mac
I'm sitting here using KDE on a P3-933 with 128Mb and it's a dog.
Seriously. AMD900 with 640Mb here, and simple stuff like starting up ark (KDE's poor attempt at a winzip clone) still takes ~7 seconds. That's a lot.
What's to blame? The reloc's/ld stuff that was reported a while back? Well, a) I'm using objprelink already; some but not too much help, and b) windows has dynamic library bindings too, how come it's not as slow? What did they do that KDE/Qt/Linux cannot?
Is it a language problem? Much bigger C-based GTK apps, like pan start up much faster than the smallest KDE C++-based app. But, again, pretty much all Windows apps are MFC based, so what did they do to improve speed?
-
Anyonymity Loves CompanyIt's hard to find someone in a crowd.
Maybe it's about time slashdroids stopped jabbering and implemented something to improve their privacy, crowds.
-
Why not use a closed network and vpn or vnc?
just a thought... why not use a closed network in the classroom that has no access outside, and then use either restricted VPN to tunnel only specific things outside, (which i guess would still allow a port 80 proxy... oops)
or a closed network and then have the students only have access to a VNC session which the profs could then session view, and display on the big screen to show what that student is doing. in addition to the "oh look, josh is net-sexing beth" types of demonstrations, the prof could also let a student run the demo showing how they did something.
sort of a new way of "brad, why dont you stand up and read that section?" -
Re:Well at least this is better then what AT&T
That is untrue.. According to the AT&T Broadband leasing agreement it states that you can run a http or ftp server on your cable modem connection. But they will not support it.
How does that jibe with the following, from http://help.broadband.att.com/legal/violations.js
p ?AT&T Broadband provides an Internet connection for personal use. Redistribution of the AT&T Broadband service is a violation of our policies. There are several ways that this could be accomplished.
FTP servers: Running an FTP server is a violation of the AT&T Broadband Terms of Service.
....
Interestingly, I can find no such clause forbidding redistribution in the leasing agreement that you quote (only a clause prohibiting *selling* services). But clearly they believe that running any kind of server is a violation. From http://help.broadband.att.com/faq.jsp?content_id=
4 16&category_id=34:Can I Host a Server?
AT&T Broadband does not allow servers to be connected to the cable modem. This means that no computer in a personal network can be used as a server.
That seems pretty clear to me! Perhaps the leasing agreement isn't the only agreement you're subject to (I notice they also have links to an "acceptable use policy", but they seem not to be accessible by non-AT&T users). In any case, I wouldn't want to have to be in the position of having to argue the point with them after they'd blocked port 80. If you want to run servers, go elsewhere if you have the choice. If that choice isn't exercised, it may eventually diseappear....
--J. Bruce Fields
-
Re:Well at least this is better then what AT&T
That is untrue.. According to the AT&T Broadband leasing agreement it states that you can run a http or ftp server on your cable modem connection. But they will not support it.
How does that jibe with the following, from http://help.broadband.att.com/legal/violations.js
p ?AT&T Broadband provides an Internet connection for personal use. Redistribution of the AT&T Broadband service is a violation of our policies. There are several ways that this could be accomplished.
FTP servers: Running an FTP server is a violation of the AT&T Broadband Terms of Service.
....
Interestingly, I can find no such clause forbidding redistribution in the leasing agreement that you quote (only a clause prohibiting *selling* services). But clearly they believe that running any kind of server is a violation. From http://help.broadband.att.com/faq.jsp?content_id=
4 16&category_id=34:Can I Host a Server?
AT&T Broadband does not allow servers to be connected to the cable modem. This means that no computer in a personal network can be used as a server.
That seems pretty clear to me! Perhaps the leasing agreement isn't the only agreement you're subject to (I notice they also have links to an "acceptable use policy", but they seem not to be accessible by non-AT&T users). In any case, I wouldn't want to have to be in the position of having to argue the point with them after they'd blocked port 80. If you want to run servers, go elsewhere if you have the choice. If that choice isn't exercised, it may eventually diseappear....
--J. Bruce Fields
-
Re:Well at least this is better then what AT&T
That is untrue.. According to the AT&T Broadband leasing agreement it states that you can run a http or ftp server on your cable modem connection. But they will not support it.
How does that jibe with the following, from http://help.broadband.att.com/legal/violations.js
p ?AT&T Broadband provides an Internet connection for personal use. Redistribution of the AT&T Broadband service is a violation of our policies. There are several ways that this could be accomplished.
FTP servers: Running an FTP server is a violation of the AT&T Broadband Terms of Service.
....
Interestingly, I can find no such clause forbidding redistribution in the leasing agreement that you quote (only a clause prohibiting *selling* services). But clearly they believe that running any kind of server is a violation. From http://help.broadband.att.com/faq.jsp?content_id=
4 16&category_id=34:Can I Host a Server?
AT&T Broadband does not allow servers to be connected to the cable modem. This means that no computer in a personal network can be used as a server.
That seems pretty clear to me! Perhaps the leasing agreement isn't the only agreement you're subject to (I notice they also have links to an "acceptable use policy", but they seem not to be accessible by non-AT&T users). In any case, I wouldn't want to have to be in the position of having to argue the point with them after they'd blocked port 80. If you want to run servers, go elsewhere if you have the choice. If that choice isn't exercised, it may eventually diseappear....
--J. Bruce Fields
-
Holy retro look, Batman!
Doesn't the phone on this page look an awful lot like the red "Hot Line" that Commissioner Gordon used to pick up with the cloth?
"Chief O'Hara, to the Batphone!"
"Aye. What's Batman's IP address again, sar?"
"Oh, forget it - you can't draw the Bat Symbol to save your life anyways... Last time we got 20 bottles of Ron Bacari Rum."
"Aye. Thet was noice, wasn't it sar?"
Soko
(Please excuse the rather poor attempt at typing in an Irish accent...) -
Re:Real Issue - 3rd party apps
You can. (Writing this sentence because some idiot running Slashdot though that the postercomment compression filter was a good idea for people who have a +1 Bonus...)
-
Want to borrow my cellular?From their contact info page:
After reading these pages and the FAQ, if you need more information, please contact:
The Broadband Phone team
AT&T Labs Cambridge
24a Trumpington Street
Cambridge CB2 1QA
United Kingdom
Email: bphone-query@uk.research.att.com
We cannot, unfortunately, answer telephone enquiries at this time.
Emphasis mine. :) -
Not just beer
According to their dload page the whole bit is also Free as in Freedom.
-
Solution
I am working on a similar project but in the >1TB range same thing applys to http://staff.sdsc.edu/its/terafile/ On that page they have a link to another page with stuff about ide-raid. >http://www.research.att.com/~gjm/linux/ide-rai d.html The 3ware cards are the way to go as they do raid 0,1,5 in hardware, and support things like hot swap and hot spare. I priced out a system that was just over 1TB of raid 5 for around $5,000 while the prebuilt stuff is $20,000.
-
objprelink
Don't forget the objprelink. I've used it to build Qt and KDE 2.2 and it has made a difference. (Although windows is still faster, UI-wise.)
-
Corporate Donations
I've been very impressed lately with the frequency and size of donations from businesses/corporations:
Microsoft donated [www.microsoft.com] $5M in cash to United Way in NY, $5M in licenses/support/tech help.
Sprint has donated [www.sprint.com] handsets and redirected a cell from NJ to NYPD. They've also provided phones for city, state and local government officials and to the American Red Cross for use in recovery efforts.
GE has pledged $10 million to a fund that will assist the families of the firefighters, police officers and emergency rescue personnel who perished while responding to the attack on the World Trade Center. [from www.ge.com]
AT&T has donated [www.att.com] $1M to American Red Cross and $10M in prepaid calling cards.
Verizon has offered [newscenter.verizon.com] free local calling to and from payphones on Manhattan streets.
I'm sure there are many more. As I look at Amazon's donation center, it looks like it's going up at about $4000/min.
This makes me proud to be an American. -
Another factual reply goes under the radarThe mention of Stroustrup is interesting. Stroustrup has a very clear opinion of Java. http://www.research.att.com/~bs/bs_faq.html#Java shows this opinion.
BTW, there is a link within that, which talks about how Java's handling of floating point is terrible and even sets back technology if fully endorsed by the industry and academia.
Java is a very young language. It is easy for me to predict that in 30 years from now, that Java's library will be a mess. For instance, Sun will have theirs along with GNU's and also don't forget other meaningful re-implemented libraries by other communities (AI, Graphics, Scientic Computation, Multimedia, etc). Java is just beginning on a long trip through computer science.
What has happened to Lisp? Algol? Smalltalk? Ada? Even C? Huge changes. That last paragraph talks about fragmentation? Let's see how Java (and C#)stand up to reality. BTW, Gosling has already said that many features should be added to Java. Read the link above for full details.
This is not flamebait. This article should be modded up to a positive number. Act like an adult and do it.
-
Loading time
What you should try to keep the loading time to a minimum is 'objprelink'. Compile QT and KDE with objprelink and nice optimizations and drop debug-info. The speedup was incredible on my machine (dual pII400 w/384MB). KDE is no longer slow
:) Even mozilla is responsive now. The 0.9.3 build that I'm using is incredible. It might have something to do with me compiling everything from scratch, but compiling just QT and KDE should do a major difference :) Objprelink can be found here: http://www.research.att.com/~leonb/objprelink/ -
Re:Exchange clone yet?
VNC is a way to remotely control a computer. The desktop of the remote computer appears in a window on your computer. If you want to run Linux on your computer, but you need to use Windows sometimes, this is one way you can do it.
http://www.uk.research.att.com/vnc/
steveha -
Re:What I want
This is exactly what I want too! The thing is that I do not need any substantial CPU on the device. Long battery life is an absolute must. This device requires hardly any CPU power and very little RAM. All it needs is a VNC client and a wireless network card. VNC servers exist for Linux as well as Windows. It is a stateful snapshot of your interface. You can disconnect and reconnect at the same point later. Oh, and did I mention that it doesn't use much CPU power?
I would like to be able to use the thing in a brighter ambient light than indoors, but I don't need that. -
Missed VNC
if ZDNet is going to review WinToNet, they should have reviewed VNC - it does essentially the same thing, and doesn't require a high-powered NT server, or Java. I've had a few problems with VNC, but the right-click works fine. I've even daisy-chained VNC sessions. My IT guy here, who's a Microsoft Man through and through, uses VNC on our servers to do remote work.
-
Re:Perhaps because few would want them?
Before we get upset and assume that there is some sort of corporate conspiracy keeping multi-OS systems off the shelfs
When I bought my Toshiba Libretto, it came preinstalled with two OSs. When first booted up, it offered a dialogue box which asked which of the two OSs you wanted to use, and then deleted the other.
What were those OSs? MS Win95 and MS Win98. But that's really not the point. Toshiba had developed an installer which allowed the machine to be shipped to the customer with multiple OSs, and allow the user to choose which he wanted. It's not just technically possible, it was judged financially worth while.
And it would have been nice if it had also shipped with Linux installed, because it's a real pain getting Linux onto one of those beaties first time. The additional cost of adding Linux would have been small, and it doesn't take much research to discover that quite a proportion of the ultra-small, ultra-geek-toy laptops run alternative OSs - just check out any geek conference you go to.
-
How about text-to-speech?My first impression was that this is kind of a waste of time. But I suppose this could be useful if you were feeding text into that nifty next-generation text-to-speech tool that was posted on Slashdot a while back.
After all, there's a difference between...
<sincere>That's a great idea</sincere>
...and...
<sarcastic>That's a great idea</sarcastic> ...that no text-to-speech program would be able to figure out without some hints.Not to mention all the different ways to say "Dude".
-
AT&T Block blocking port 80 due to Code Red
Last week AT&T Broadband's solution to stopping port 80 was just to completely block all incomming packet going to port 80. See the 7/30 accouncement. Its to bad they had to cop out and filter this network wide. Its to bad I can't get speakeasy dsl in my area yet because I would have switch over in an instant.
-
FUD alert
I recently read an article where Bjarne outlined many of the things he had on the C++ wishlist, which more or less were the steps to make C++ into Java.
Stroustrup's presentation notes can be found here (PDF format). I invite anyone interested in knowing what he actually said to take a look. It certainly doesn't sound much like Java to me.
-
Object Prelink optimization improves startup time
This speeds up KDE program startup times by 50% by precomputing offsets used by the dynamic linker.
-
The future of C++
Language writers should put their creativity into extending C++ rather than abandoning it.
They are. The C++ standards committee deliberately left C++ in a known, standardised state for three years or so to allow some stability for developers using it. They are now actively working on C++0x, the next revision to the standard, currently expected some time 2003-2005. (That's level with, or ahead of, fully
.NET supporting versions of Windoze, BTW. C# advocates, eat your hearts out.)Strange as it may seem to some of the posters around here, the serious guys have actually noticed that people want to see inter-language communication, threading, yada yada, too. Members of the committee, including Stroustrup himself, have several stated goals for C++0x, including:
- removing some of the most common complaints about C++ as it stands (syntax oddities and the like);
- making C++ easier to teach properly (since most teaching of C++ at the moment is terrible, which is the single biggest problem the language has);
- ambitious extensions to the library (likely to include a framework for threading, RPC, etc);
- better support for interfacing with other programming languages, and for use with architectures using "components" (CORBA, COM, EJB, and so on).
So, before everyone gets off on talking about C++ with 15-years-out-of-date knowledge as usual, please remember that the language is still being worked on, is still improving and is still adapting to the rest of the marketplace. While people on
/. buzzword themselves to death, the pro's using solid tools like C++ will continue to do so. More details, as ever, can be found on the comp.std.c++ newsgroup. -
Re:No blocking yetThis came from their broadband page.
http://help.broadband.att.com/faq.jsp?content_id=
4 16&category_id=34 -
Re:You're violating our Double Secret AUP!
Yep, I agree completely. The original poster's reference comes from this little item. But in their publicly available documents I've not been able to find where they define "server". I also find it odd that they have different service requirements and policies depending on your location. Obviously some of that is dependent on the equipment installed in a particular area and any contractual things that a local franchising agency might require. I know that many AT&T@Home customers are required to use DHCP for example. Where I'm located, we can request static IPs at no extra charge even though the printed contract I was given says otherwise.
-
Re:Cutting off port 80
-
AT&T Port 80 Blocking Ineffective, Irresponsible
The version of AT&T's Broadband Subscriber Agreement that subscribers in my area (Formerly MediaOne Express) have agreed to could only be vaguely construed to prohibit web servers via the following clause:
(g) restrict, inhibit or otherwise interfere with the ability of any other person to use or enjoy the AT&T Equipment or the Service, including, without limitation, posting or transmitting any information or software which contains a virus or other harmful feature; or generating levels of traffic sufficient to impede others' ability to send or retrieve information.
Indeed, the service agreement even mentions things users should consider should they decide to run a personal HTTP/FTP server:
(b) FTP/HTTP Service Setup. Customer should be aware that when using the Service to access the Internet or any other online network or service, there are certain applications, such as FTP (File Transfer Protocol) server or HTTP (Hyper Text Transfer Protocol) server, which may be used to allow other Service users and Internet users to gain access to Customer's computer. If Customer chooses to run such applications, Customer should take the appropriate security measures. Neither AT&T nor @Home Network shall have any liability whatsoever for any claims, losses, actions, damages, suits or proceedings resulting from, arising out of or otherwise relating to the use of such applications by Customer, including without limitation, damages resulting from others accessing Customer's computer.
See http://help.broadband.att.com/subagreelease.jsp for the full text of the subscriber agreement.
AT&T is trying to use the subscriber agreement as a shield against criticism about how they've failed to properly deal with their network's accute inability to handle widespread use of the codered software by subscribers and also their inability to selectively track and remove or restrict users of codered. Running a webserver like IIS+codered that by design, defect, or configuration tries repeatedly to install a software package on every other webserver on the network is surely a prohibited use of the service under the subscriber agreement. Running a web server that only implements RFC2068 and has none of these annoying codered misfeatures probably isn't.
The most effective thing AT&T could do to stop the autoinstallation of codered on customer machines is to block port 80 right at the cable modem on hosts running versions of IIS that support codered. It's certainly within their technical reach, since AT&T does selective layer-3 filtering of ports 137-139 right at the cable per customer request. For hosts that both support and run codered, AT&T should treat the host like they would treat any other compromised host: disconnect it from the network until the owner has recovered control.
Instead of using any of the more effective methods, they're just having routers discard packets bound for port 80. Not only does this solution fail to prevent autoinstallation within AT&T subnets (because that traffic never crosses a router) and from hosts inside AT&T's network to those hosts outside of AT&T's network, but it also inconveniences legitimate users of port 80.
-
Re:No blocking yetThat's odd. There isn't any such clause in the subscriber agreement that the AT&T page listed at in the Slashdot announcement links to.
Could you provide a URL for what you are quoting?
The explanation given and the clause given as an excuse are (quoting from the above links) an extremely long stretch in IMO:
Why Can't AT&T@Home Residential Customers Run Web Servers?
The AT&T@Home residential service offering is a consumer product designed for your personal use of the Internet. Customers must ensure that their activity does not improperly restrict, inhibit, or degrade any other user's use of the Services, nor represent (in the sole judgment of AT&T Broadband) an unusually large burden on the network itself.
The benefits and privileges available from the AT&T@Home, and the Internet in general, must be balanced with duties and responsibilities so that other customers can also have a productive experience.
Under the terms of the AT&T Broadband Subscriber Agreement customers are not to restrict, inhibit or otherwise interfere with the ability of any other person to use or enjoy the AT&T Equipment or the Service. See Prohibited Uses of Service (g) in the AT&T@Home Subscriber Agreement.
The clause referred to:
g) restrict, inhibit or otherwise interfere with the ability of any other person to use or enjoy the AT&T Equipment or the Service, including, without limitation, posting or transmitting any information or software which contains a virus or other harmful feature; or generating levels of traffic sufficient to impede others' ability to send or retrieve information;
So, where do they get off filtering a small, low-bandwidth server that doesn't do what "clause g" prohibits?
-
Re:No blocking yetThat's odd. There isn't any such clause in the subscriber agreement that the AT&T page listed at in the Slashdot announcement links to.
Could you provide a URL for what you are quoting?
The explanation given and the clause given as an excuse are (quoting from the above links) an extremely long stretch in IMO:
Why Can't AT&T@Home Residential Customers Run Web Servers?
The AT&T@Home residential service offering is a consumer product designed for your personal use of the Internet. Customers must ensure that their activity does not improperly restrict, inhibit, or degrade any other user's use of the Services, nor represent (in the sole judgment of AT&T Broadband) an unusually large burden on the network itself.
The benefits and privileges available from the AT&T@Home, and the Internet in general, must be balanced with duties and responsibilities so that other customers can also have a productive experience.
Under the terms of the AT&T Broadband Subscriber Agreement customers are not to restrict, inhibit or otherwise interfere with the ability of any other person to use or enjoy the AT&T Equipment or the Service. See Prohibited Uses of Service (g) in the AT&T@Home Subscriber Agreement.
The clause referred to:
g) restrict, inhibit or otherwise interfere with the ability of any other person to use or enjoy the AT&T Equipment or the Service, including, without limitation, posting or transmitting any information or software which contains a virus or other harmful feature; or generating levels of traffic sufficient to impede others' ability to send or retrieve information;
So, where do they get off filtering a small, low-bandwidth server that doesn't do what "clause g" prohibits?
-
Actually...
Their TOS has a clause that explicitly says you can run FTP/HTTP servers (section 9.b):
(b) FTP/HTTP Service Setup. Customer should be aware that when using the Service to access the Internet or any other online network or service, there are certain applications, such as FTP (File Transfer Protocol) server or HTTP (Hyper Text Transfer Protocol) server, which may be used to allow other Service users and Internet users to gain access to Customer's computer. If Customer chooses to run such applications, Customer should take the appropriate security measures. Neither AT&T nor @Home Network shall have any liability whatsoever for any claims, losses, actions, damages, suits or proceedings resulting from, arising out of or otherwise relating to the use of such applications by Customer, including without limitation, damages resulting from others accessing Customer's computer.
Of course, they still have the "right" to block port 80, but users can still set up web servers. -
If you're in Eastern Mass. AT&T's lyingAT&T "Customer Service" is claiming that their Acceptable Use Policy forbids servers. This is not true for all customers; I know it's not true at least for the former customers of MediaOne in Eastern Massachusetts.
Partially quoted from:
roadrunner.techtalk.general
3B709BDA.3480@mediaone.net.invalid
chelm@mediaone.net.invalid wrote:
Posting to ATT/RR Home Page on transition to Excited@Home:
Which states:New Service Subscriber Agreement
"AT&T@Home Subscriber Agreement" links to:Your AT&T Road Runner home page will automatically change to the new content provided by AT&T @Home on June 30, 2001. Effective with the elimination of the Road Runner content, the AT&T Road Runner Service Subscriber Agreement will be replaced with the AT&T@Home Subscriber Agreement. You can see the new agreement at http://help.broadband.att.com/support under the Policies section of Answers to Questions. Because you are not using @Home software, the @Home End User License Agreement attached to the end of your new agreement will not apply to you.
http://help.broadband.att.com/support/faq.jsp?cont ent_id=584&category_id=34
which leads to:
http://help.broadband.att.com/subagreelease.jsp9. Service Characteristics
And furthermore from the same document:(b) FTP/HTTP Service Setup. Customer should be aware that when using the Service to access the Internet or any other online network or service, there are certain applications, such as FTP (File Transfer Protocol) server or HTTP (Hyper Text Transfer Protocol) server, which may be used to allow other Service users and Internet users to gain access to Customer's computer. If Customer chooses to run such applications, Customer should take the appropriate security measures. Neither AT&T nor @Home Network shall have any liability whatsoever for any claims, losses, actions, damages, suits or proceedings resulting from, arising out of or otherwise relating to the use of such applications by Customer, including without limitation, damages resulting from others accessing Customer's computer.
(c) File and Print Sharing. The Service functions as a Local Area Network (LAN) in that each Customer is a node on the network. As such, users outside the Customer's home may be able to access the Customer's computer. As well, some software includes capabilities that permit other users across a network such as the Service and the Internet to gain access to the Customer's computer and to the software, files and data stored on the computer. For example, operating systems such as Windows 95 and Apple Macintosh include file sharing and print sharing capabilities which, when enabled, will permit other users to gain access to the Customer's computer even if the Customer is not using the Service. AT&T therefore recommends that the Customer connect only a single computer to the Service and that the Customer disable file and print sharing and other capabilities that allow users to gain access to the Customer's computer. Any Customer who chooses to participate in the Service using other than a single computer or who chooses to enable capabilities such as file sharing, print sharing, or other capabilities that allow users to gain access to the Customer's computer, hereby acknowledges and agrees that the Customer does so at the Customer's own risk, and that neither AT&T nor @Home Network shall have any liability whatsoever for any claims, losses, actions, damages, suits or proceedings arising out of or otherwise relating to such use by the Customer.
11. Miscellaneous
Did anyone else get notification before port 80 was blocked? The above policies certianly still seem to be in effect; they're still posted and they clearly imply customers may run HTTP & FTP servers at their own risk.(b) Amendment. AT&T may, in it sole discretion, change, modify, add or remove portions of this Agreement, and the Service provided thereunder, at any time. AT&T will notify Customer of any such changes by posting notice of such changes on the Service, or sending notice via e-mail, postal mail or other means. Customer's continued use of the Service following notice of such change shall be deemed to be Customer's acceptance of any such modification. If Customer does not agree to any such modification, Customer must immediately stop using the Service and notify AT&T that Customer is terminating this Agreement in accordance with Section 7(a) of this Agreement. Customer will then be entitled to a refund of any unused portion of any monthly Service fee that has been paid in advance.
-
If you're in Eastern Mass. AT&T's lyingAT&T "Customer Service" is claiming that their Acceptable Use Policy forbids servers. This is not true for all customers; I know it's not true at least for the former customers of MediaOne in Eastern Massachusetts.
Partially quoted from:
roadrunner.techtalk.general
3B709BDA.3480@mediaone.net.invalid
chelm@mediaone.net.invalid wrote:
Posting to ATT/RR Home Page on transition to Excited@Home:
Which states:New Service Subscriber Agreement
"AT&T@Home Subscriber Agreement" links to:Your AT&T Road Runner home page will automatically change to the new content provided by AT&T @Home on June 30, 2001. Effective with the elimination of the Road Runner content, the AT&T Road Runner Service Subscriber Agreement will be replaced with the AT&T@Home Subscriber Agreement. You can see the new agreement at http://help.broadband.att.com/support under the Policies section of Answers to Questions. Because you are not using @Home software, the @Home End User License Agreement attached to the end of your new agreement will not apply to you.
http://help.broadband.att.com/support/faq.jsp?cont ent_id=584&category_id=34
which leads to:
http://help.broadband.att.com/subagreelease.jsp9. Service Characteristics
And furthermore from the same document:(b) FTP/HTTP Service Setup. Customer should be aware that when using the Service to access the Internet or any other online network or service, there are certain applications, such as FTP (File Transfer Protocol) server or HTTP (Hyper Text Transfer Protocol) server, which may be used to allow other Service users and Internet users to gain access to Customer's computer. If Customer chooses to run such applications, Customer should take the appropriate security measures. Neither AT&T nor @Home Network shall have any liability whatsoever for any claims, losses, actions, damages, suits or proceedings resulting from, arising out of or otherwise relating to the use of such applications by Customer, including without limitation, damages resulting from others accessing Customer's computer.
(c) File and Print Sharing. The Service functions as a Local Area Network (LAN) in that each Customer is a node on the network. As such, users outside the Customer's home may be able to access the Customer's computer. As well, some software includes capabilities that permit other users across a network such as the Service and the Internet to gain access to the Customer's computer and to the software, files and data stored on the computer. For example, operating systems such as Windows 95 and Apple Macintosh include file sharing and print sharing capabilities which, when enabled, will permit other users to gain access to the Customer's computer even if the Customer is not using the Service. AT&T therefore recommends that the Customer connect only a single computer to the Service and that the Customer disable file and print sharing and other capabilities that allow users to gain access to the Customer's computer. Any Customer who chooses to participate in the Service using other than a single computer or who chooses to enable capabilities such as file sharing, print sharing, or other capabilities that allow users to gain access to the Customer's computer, hereby acknowledges and agrees that the Customer does so at the Customer's own risk, and that neither AT&T nor @Home Network shall have any liability whatsoever for any claims, losses, actions, damages, suits or proceedings arising out of or otherwise relating to such use by the Customer.
11. Miscellaneous
Did anyone else get notification before port 80 was blocked? The above policies certianly still seem to be in effect; they're still posted and they clearly imply customers may run HTTP & FTP servers at their own risk.(b) Amendment. AT&T may, in it sole discretion, change, modify, add or remove portions of this Agreement, and the Service provided thereunder, at any time. AT&T will notify Customer of any such changes by posting notice of such changes on the Service, or sending notice via e-mail, postal mail or other means. Customer's continued use of the Service following notice of such change shall be deemed to be Customer's acceptance of any such modification. If Customer does not agree to any such modification, Customer must immediately stop using the Service and notify AT&T that Customer is terminating this Agreement in accordance with Section 7(a) of this Agreement. Customer will then be entitled to a refund of any unused portion of any monthly Service fee that has been paid in advance.
-
If you're in Eastern Mass. AT&T's lyingAT&T "Customer Service" is claiming that their Acceptable Use Policy forbids servers. This is not true for all customers; I know it's not true at least for the former customers of MediaOne in Eastern Massachusetts.
Partially quoted from:
roadrunner.techtalk.general
3B709BDA.3480@mediaone.net.invalid
chelm@mediaone.net.invalid wrote:
Posting to ATT/RR Home Page on transition to Excited@Home:
Which states:New Service Subscriber Agreement
"AT&T@Home Subscriber Agreement" links to:Your AT&T Road Runner home page will automatically change to the new content provided by AT&T @Home on June 30, 2001. Effective with the elimination of the Road Runner content, the AT&T Road Runner Service Subscriber Agreement will be replaced with the AT&T@Home Subscriber Agreement. You can see the new agreement at http://help.broadband.att.com/support under the Policies section of Answers to Questions. Because you are not using @Home software, the @Home End User License Agreement attached to the end of your new agreement will not apply to you.
http://help.broadband.att.com/support/faq.jsp?cont ent_id=584&category_id=34
which leads to:
http://help.broadband.att.com/subagreelease.jsp9. Service Characteristics
And furthermore from the same document:(b) FTP/HTTP Service Setup. Customer should be aware that when using the Service to access the Internet or any other online network or service, there are certain applications, such as FTP (File Transfer Protocol) server or HTTP (Hyper Text Transfer Protocol) server, which may be used to allow other Service users and Internet users to gain access to Customer's computer. If Customer chooses to run such applications, Customer should take the appropriate security measures. Neither AT&T nor @Home Network shall have any liability whatsoever for any claims, losses, actions, damages, suits or proceedings resulting from, arising out of or otherwise relating to the use of such applications by Customer, including without limitation, damages resulting from others accessing Customer's computer.
(c) File and Print Sharing. The Service functions as a Local Area Network (LAN) in that each Customer is a node on the network. As such, users outside the Customer's home may be able to access the Customer's computer. As well, some software includes capabilities that permit other users across a network such as the Service and the Internet to gain access to the Customer's computer and to the software, files and data stored on the computer. For example, operating systems such as Windows 95 and Apple Macintosh include file sharing and print sharing capabilities which, when enabled, will permit other users to gain access to the Customer's computer even if the Customer is not using the Service. AT&T therefore recommends that the Customer connect only a single computer to the Service and that the Customer disable file and print sharing and other capabilities that allow users to gain access to the Customer's computer. Any Customer who chooses to participate in the Service using other than a single computer or who chooses to enable capabilities such as file sharing, print sharing, or other capabilities that allow users to gain access to the Customer's computer, hereby acknowledges and agrees that the Customer does so at the Customer's own risk, and that neither AT&T nor @Home Network shall have any liability whatsoever for any claims, losses, actions, damages, suits or proceedings arising out of or otherwise relating to such use by the Customer.
11. Miscellaneous
Did anyone else get notification before port 80 was blocked? The above policies certianly still seem to be in effect; they're still posted and they clearly imply customers may run HTTP & FTP servers at their own risk.(b) Amendment. AT&T may, in it sole discretion, change, modify, add or remove portions of this Agreement, and the Service provided thereunder, at any time. AT&T will notify Customer of any such changes by posting notice of such changes on the Service, or sending notice via e-mail, postal mail or other means. Customer's continued use of the Service following notice of such change shall be deemed to be Customer's acceptance of any such modification. If Customer does not agree to any such modification, Customer must immediately stop using the Service and notify AT&T that Customer is terminating this Agreement in accordance with Section 7(a) of this Agreement. Customer will then be entitled to a refund of any unused portion of any monthly Service fee that has been paid in advance.
-
If you're in Eastern Mass. AT&T's lyingAT&T "Customer Service" is claiming that their Acceptable Use Policy forbids servers. This is not true for all customers; I know it's not true at least for the former customers of MediaOne in Eastern Massachusetts.
Partially quoted from:
roadrunner.techtalk.general
3B709BDA.3480@mediaone.net.invalid
chelm@mediaone.net.invalid wrote:
Posting to ATT/RR Home Page on transition to Excited@Home:
Which states:New Service Subscriber Agreement
"AT&T@Home Subscriber Agreement" links to:Your AT&T Road Runner home page will automatically change to the new content provided by AT&T @Home on June 30, 2001. Effective with the elimination of the Road Runner content, the AT&T Road Runner Service Subscriber Agreement will be replaced with the AT&T@Home Subscriber Agreement. You can see the new agreement at http://help.broadband.att.com/support under the Policies section of Answers to Questions. Because you are not using @Home software, the @Home End User License Agreement attached to the end of your new agreement will not apply to you.
http://help.broadband.att.com/support/faq.jsp?cont ent_id=584&category_id=34
which leads to:
http://help.broadband.att.com/subagreelease.jsp9. Service Characteristics
And furthermore from the same document:(b) FTP/HTTP Service Setup. Customer should be aware that when using the Service to access the Internet or any other online network or service, there are certain applications, such as FTP (File Transfer Protocol) server or HTTP (Hyper Text Transfer Protocol) server, which may be used to allow other Service users and Internet users to gain access to Customer's computer. If Customer chooses to run such applications, Customer should take the appropriate security measures. Neither AT&T nor @Home Network shall have any liability whatsoever for any claims, losses, actions, damages, suits or proceedings resulting from, arising out of or otherwise relating to the use of such applications by Customer, including without limitation, damages resulting from others accessing Customer's computer.
(c) File and Print Sharing. The Service functions as a Local Area Network (LAN) in that each Customer is a node on the network. As such, users outside the Customer's home may be able to access the Customer's computer. As well, some software includes capabilities that permit other users across a network such as the Service and the Internet to gain access to the Customer's computer and to the software, files and data stored on the computer. For example, operating systems such as Windows 95 and Apple Macintosh include file sharing and print sharing capabilities which, when enabled, will permit other users to gain access to the Customer's computer even if the Customer is not using the Service. AT&T therefore recommends that the Customer connect only a single computer to the Service and that the Customer disable file and print sharing and other capabilities that allow users to gain access to the Customer's computer. Any Customer who chooses to participate in the Service using other than a single computer or who chooses to enable capabilities such as file sharing, print sharing, or other capabilities that allow users to gain access to the Customer's computer, hereby acknowledges and agrees that the Customer does so at the Customer's own risk, and that neither AT&T nor @Home Network shall have any liability whatsoever for any claims, losses, actions, damages, suits or proceedings arising out of or otherwise relating to such use by the Customer.
11. Miscellaneous
Did anyone else get notification before port 80 was blocked? The above policies certianly still seem to be in effect; they're still posted and they clearly imply customers may run HTTP & FTP servers at their own risk.(b) Amendment. AT&T may, in it sole discretion, change, modify, add or remove portions of this Agreement, and the Service provided thereunder, at any time. AT&T will notify Customer of any such changes by posting notice of such changes on the Service, or sending notice via e-mail, postal mail or other means. Customer's continued use of the Service following notice of such change shall be deemed to be Customer's acceptance of any such modification. If Customer does not agree to any such modification, Customer must immediately stop using the Service and notify AT&T that Customer is terminating this Agreement in accordance with Section 7(a) of this Agreement. Customer will then be entitled to a refund of any unused portion of any monthly Service fee that has been paid in advance.
-
Re:Read the Acceptabel Use Agreementhttp://help.broadband.att.com/faq.jsp?content_id=
5 84&category_id=34Choose either one, weather you leased your modem or purchased, either or there's a clause that allows you to host both a FTP server and an HTTP server.
-
Re:Cutting off port 80?
Here's AT&T's e-mail response from Tuesday morning:
Thank you for contacting AT&T BroadBand Cable Internet Service.
We have blocked port 80 as a temporary measure and will be lifting the block when our network engineers have finished their work. I do not have an estimated time for this, however. I apologize for any inconvenience that you may be experiencing.
During a Tuesday afternoon chat session, another one of their support reps stated:
We may have some more information regarding port 80 later this evening, otherwise you could check back tomorrow for possible updates. I do apologize for the inconvenience.
On the chat session, whoever answered the chat at least knew about the port 80 block so the word is getting out within AT&T support - not like Monday when they were totally clueless. The online Network Status is still vague "We are experiencing service interruptions affecting All Regions that may cause intermittent network connectivity. "
As for whether or not AT&T allows servers is up for debate. Their 2nd level tech support said they don't, but I quoted the leased line subscriber agreement, located http://help.broadband.att.com/subagreelease.jsp, specifically section 9b that says that servers are allowed. -
Re:mediaone EUA ALLOWS FTP AND HTTP SERVERS
I sorta read that the same way, unfortunately it is contradicted by the AUP which says:
Examples of prohibited uses include, but are not limited to, running servers for mail, http, ftp, irc, and dhcp, and multi-user interactive forums.
Also, you'll find a Q&A that says:
AT&T Broadband does not allow servers to be connected to the cable modem. This means that no computer in a personal network can be used as a server.
They also say in their AUP that they don't spy on their customers and don't go out of their way to catch people. Essentially, if you're running a server that is *not* causing bandwidth problems for your neighbors, they won't come after you. -
Re:Cutting off port 80HEY! It's not against their AUP to run a web server!
From: http://help.broadband.att.com/subagreelease.jsp
(b) FTP/HTTP Service Setup. Customer should be aware that when using the Service to access the Internet or any other online network or service, there are certain applications, such as FTP (File Transfer Protocol) server or HTTP (Hyper Text Transfer Protocol) server, which may be used to allow other Service users and Internet users to gain access to Customer's computer. If Customer chooses to run such applications, Customer should take the appropriate security measures. Neither AT&T nor @Home Network shall have any liability whatsoever for any claims, losses, actions, damages, suits or proceedings resulting from, arising out of or otherwise relating to the use of such applications by Customer, including without limitation, damages resulting from others accessing Customer's computer.
And the actual AUP page doesn't mention it at all: http://help.broadband.att.com/faq.jsp?content_id=
7 2&category_id=34 -
Re:Cutting off port 80HEY! It's not against their AUP to run a web server!
From: http://help.broadband.att.com/subagreelease.jsp
(b) FTP/HTTP Service Setup. Customer should be aware that when using the Service to access the Internet or any other online network or service, there are certain applications, such as FTP (File Transfer Protocol) server or HTTP (Hyper Text Transfer Protocol) server, which may be used to allow other Service users and Internet users to gain access to Customer's computer. If Customer chooses to run such applications, Customer should take the appropriate security measures. Neither AT&T nor @Home Network shall have any liability whatsoever for any claims, losses, actions, damages, suits or proceedings resulting from, arising out of or otherwise relating to the use of such applications by Customer, including without limitation, damages resulting from others accessing Customer's computer.
And the actual AUP page doesn't mention it at all: http://help.broadband.att.com/faq.jsp?content_id=
7 2&category_id=34 -
bandwidth is cheap? On what planet?
So who cares about compression. Personally, I'd much prefer the open and obvious standards of XML to some obfuscated form. Data is confusing enough already; at least XML gives a clear description that I can use with a packet sniffer when trying to debug something.
You're kidding right? Most CS people I know cringe at the fact that XML can more than double the size of a document with largely redundant tags. The only thing to be thankful for is that the documents typically compress very well due to the large number of redundant tags and that HTTP 1.1 supports compression especially know that XML over HTTP (i.e. web services) is being beaten to death by a lot of people in the software industry. Numerous articles about XML compression also tend to disagree with you that it is not an issue.
PS: If bandwidth is so cheap how come DSL companies are going out of business and AOL owns Time Warner? This would tend to imply that low bandwidth connections are still the order of the day. -
Re:Cutting off port 80
If you check the at&t roadrunner subscriber agreement, you will see that it only mentions running those services for commercial purposes. As long as you are are no reselling/redirecting traffic, its perfectly legal to run your own servers.
-
mediaone EUA ALLOWS FTP AND HTTP SERVERS
EUA states in section 9(b) this:
9. Service Characteristics
(b) FTP/HTTP Service Setup. Customer should be aware that when using the Service to access the Internet or any other online network or service, there are certain applications, such as FTP (File Transfer Protocol) server or HTTP (Hyper Text Transfer Protocol) server, which may be used to allow other Service users and Internet users to gain access to Customer's computer. If Customer chooses to run such applications, Customer should take the appropriate security measures. Neither AT&T nor @Home Network shall have any liability whatsoever for any claims, losses, actions, damages, suits or proceedings resulting from, arising out of or otherwise relating to the use of such applications by Customer, including without limitation, damages resulting from others accessing Customer's computer.
-
Port 80 blocking on AT&T (aka Mediaone segment)My server was blocked at 9AM on August 5th. I use it mostly for my resume. I have since relocated my server to port 8080 and it works fine again. I also spoke with a couple different people concerning their blocking port 80, and they totally deny it.
Wow, that's kind of weird considering the traffic ended at EXACTLY 9AM for old pages I used to host on that server. And wow, someone couldn't get to my resume that day, and emailed me about the problem they had. Very odd. I don't have a problem if they are going to block it for whatever reason, but at least admit it in the Agreement. I just want it for personal use...
-
Port 80 blocking on AT&T (aka Mediaone segment)My server was blocked at 9AM on August 5th. I use it mostly for my resume. I have since relocated my server to port 8080 and it works fine again. I also spoke with a couple different people concerning their blocking port 80, and they totally deny it.
Wow, that's kind of weird considering the traffic ended at EXACTLY 9AM for old pages I used to host on that server. And wow, someone couldn't get to my resume that day, and emailed me about the problem they had. Very odd. I don't have a problem if they are going to block it for whatever reason, but at least admit it in the Agreement. I just want it for personal use...
-
Port 80 blocking on AT&T (aka Mediaone segment)My server was blocked at 9AM on August 5th. I use it mostly for my resume. I have since relocated my server to port 8080 and it works fine again. I also spoke with a couple different people concerning their blocking port 80, and they totally deny it.
Wow, that's kind of weird considering the traffic ended at EXACTLY 9AM for old pages I used to host on that server. And wow, someone couldn't get to my resume that day, and emailed me about the problem they had. Very odd. I don't have a problem if they are going to block it for whatever reason, but at least admit it in the Agreement. I just want it for personal use...
-
Speed: Just improved by 30% !!I guess you mean startup speed, because normal speed was already quite OK.
KDE-2.2 is quite a lot (noticably) faster than KDE-2.1.1. Especially file management is a lot faster now, but also configuration dialogs and so on. Not as fast as Win95, but fast enough to feel snappy (on my P-ii-300).
If you are interested in startup speed, check out the objprelink hack for C++ projects, that was just recently done for KDE. It improves startup times of KDE apps by 30-50 % and might also be of use for OpenOffice, Mozilla and other large C++ applications. Of course it is just a hack until real (stable) prelinking in gcc is available. Note: This has not been included to KDE-2.2 by default, because it arrived during the feature freeze. Hopefully your packager will use this or just follow the step-by-step instructions yourself. It is easy and works like advertised.
:-) Have fun KDE folks!