Article View: ahn.tech.linux
Article #906Re: this is Bellsouth policy.
From: charlieman
Date: Thu, 05 Apr 2001 02:46
Date: Thu, 05 Apr 2001 02:46
111 lines
6962 bytes
6962 bytes
what is the bridging that your talking about? "Stray Cat" <Stray_Cat@alt.anonymous.messages> wrote in message news:gamkctgv5g1j5pi8fa69oi9985l7igk1jj@localhost... > On Tue, 03 Apr 2001 22:34:21 GMT, kryppy@bellsouth.net (Jack Agent > 3509) wrote: > > >On Tue, 03 Apr 2001 01:55:40 -0400, Stray Cat > ><Stray_Cat@alt.anonymous.messages> wrote: > > > >>On Tue, 03 Apr 2001 05:03:14 GMT, kryppy@bellsouth.net (Jack Agent > >>3509) wrote: > >> > >>>On Mon, 02 Apr 2001 17:25:02 -0400, John M. <none@none.com> wrote: > >>> > >>>>A happy Bellsouth customer without a decent news server? > >>> > >>>I would be a happy Bellsouth customer even if they just discontinued > >>>the damn newservers already. They have pretty much always sucked > >>>anyway. > >>> > >>>On the other hand, you could always get a T-1 and then for your $1000 > >>>per month you will have to buy a premium newservice anyway.. > >>> > >>>You pay $50 for this service...come on. No affordable home broadband > >>>can even come close to this!! Hell they could also can the stinking > >>>mail servers for all I care. > >> > >>Really? I pay $50, and get good news and mail (but I don't use the > >>mail, I run my own). > > > >Does Telocity's newservers really compare to alt, supernews or any of > >the premium servers?? When they eventually force me off my bridged > >connection I will probably get to see firsthand... > > Sure. When the server was in top shape completion and speed were > absolutely stellar. It more than rivaled commercial services, it was > clearly better. These days completion in now good again, but not quite > as good as it was. Speed is off a bit during peak hours, but great > during the day. There is interaction between the completion and the > speed. When the server is under heavy reading load, completion can > start to slip. But it a very good freebie still. > > Given Bellsouth's now public admission that bridging will be > deprecated, that ought to clinch it for those who find this important > to them. How many will wait till it's gone before actually going > elsewhere is the big question. My feel is that the longer you postpone > the inevitable, the greater the chance that a change will be more > difficult or not turn out as well. Of course Bellsouth's performance > to schedules could mean that bridging will be around a lot longer than > they are saying now. But so is that news server fiasco that was > supposed to be cleared up by April 2000. I wouldn't count on this > though. > > >>>Who wants their IP and all that BS crap in the headers anyway? > >> > >>My ISP's news server doesn't put IPs in the headers. But they still > >>can know who made the post. > > > >I'm pretty sure anyone running a newserver could tell who made a post > >in question, the difference is just seeing it in the headers or > >obtaining a court order. > > Anyone running a news server can tell who made posts if they keep > logs. They don't need a court order to read their own logs. They may > require a court order to reveal that information to interested third > parties, but plenty of them will roll over without any legal paperwork > at all. > > > > >>>One warez post and you would be back on dialup... > >> > >>LOL. And you'd lose that account too on the next illegal post if you > >>upped it directly to a news server. Unless the server was in Russia or > >>some such place. > > > > > >I'm talking about the difference in upping warez from your bellsouth > >server vs say alt.net's servers. With one you MAY lose your news > >account - the other...back on dialup....or the next broadband > >provider... > > > > Sure. But you might not even lose your news account on alt.net. You > will have to deal with the legal problems yourself, alt.net doesn't > get involved in that. They just surrender evidence. But everyone gets > a second chance there, at least. > > All you have to do is re-affirm that you won't use the service in ways > that are against the AUP. In fact, I don't know anyone who actually > got shut off for warezing. They generated some posts that led to > complaints, the complaints were forwarded to the poster and they had > to reply that they got the complaint and that they would abide by the > AUP. > > The tone of the letter is completely non-accusatory. They don't say > you did anything wrong or illegal, just that someone complained, and > if what they say happened is true, it might be a problem. > > The only catch with this is that you can't ignore the letter. They > will send e-mail to your address on record and if you ignore it or it > bounces, they may disable your ability to post until you get in touch > with them about this. > > But sure, posting something bad to a Bellsouth news server wouldn't be > smart if you could do it another way, even if you had to pay for that > other way. However, it's a matter of degree. If someone complains to > altnet, for example, they get your name and the IP you used too. There > is nothing to prevent the complainant from also whining to Bellsouth > about illegal use of the service. Check your AUP on this. It doesn't > say illegal acts on their servers, it says illegal acts using their > network.
Technical Details
Message-ID:
<X%Qy6.3190$Rv.138528@news1.atl>Path:
arc1-ca.pugleaf.net!supernews.google.com!sn-xit-03!supernews.com!freenix!sunqbc.risq.qc.ca!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news1.atl.POSTED!not-for-mailReferences:
<6uDw6.2219$tG3.154721@news1.atl> <R85y6.698$al2.47990@news2.atl> <rl5y6.715$al2.48338@news2.atl> <bgrhctge7h9nnoe3qbjmkt0u5ls6qj9pcd@4ax.com> <3aca56d5.93572417@news2.mia.bellsouth.net> <uroictoc1dgpsmsbs0sfqhcr1db7egp7pq@localhost> <3acc4e1f.156888570@news.mia.bellsouth.net> <gamkctgv5g1j5pi8fa69oi9985l7igk1jj@localhost>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f8a83,4fb12e5c197b5c69 X-Google-Attributes: gidf8a83,public X-Google-Thread: 1122a6,4fb12e5c197b5c69 X-Google-Attributes: gid1122a6,public X-Google-Thread: ff611,4fb12e5c197b5c69 X-Google-Attributes: gidff611,public X-Google-Thread: f9b51,4fb12e5c197b5c69 X-Google-Attributes: gidf9b51,public X-Google-Thread: 11033e,4fb12e5c197b5c69 X-Google-Attributes: gid11033e,public X-Google-ArrivalTime: 2001-04-04 19:48:03 PST Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-03!supernews.com!freenix!sunqbc.risq.qc.ca!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news1.atl.POSTED!not-for-mail Reply-To: "charlieman" <charlieman@bellsouth.netSPAM> From: "charlieman" <charlieman@bellsouth.netSPAM> Newsgroups: ahn.tech.linux,alt.os.linux.mandrake,bellsouth.net.support.adsl,bellsouth.net.support.linux,comp.os.linux.setup References: <6uDw6.2219$tG3.154721@news1.atl> <R85y6.698$al2.47990@news2.atl> <rl5y6.715$al2.48338@news2.atl> <bgrhctge7h9nnoe3qbjmkt0u5ls6qj9pcd@4ax.com> <3aca56d5.93572417@news2.mia.bellsouth.net> <uroictoc1dgpsmsbs0sfqhcr1db7egp7pq@localhost> <3acc4e1f.156888570@news.mia.bellsouth.net> <gamkctgv5g1j5pi8fa69oi9985l7igk1jj@localhost> Subject: Re: this is Bellsouth policy. Lines: 113 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: <X%Qy6.3190$Rv.138528@news1.atl> Date: Wed, 4 Apr 2001 21:46:55 -0500 NNTP-Posting-Host: 66.20.110.81 X-Trace: news1.atl 986438775 66.20.110.81 (Wed, 04 Apr 2001 22:46:15 EDT) NNTP-Posting-Date: Wed, 04 Apr 2001 22:46:15 EDT