🚀 go-pugleaf

"BigPecs8" wrote in message 
news:4548b402$0$23925$9a6e19ea@unlimited.newshosting.com...


<snip - same drivel multiposted in other groups>

You didn't fool anyone over at 24hoursupport.helpdesk, either, where 
you cross-posted to the UNRELATED newsgroups 
3b.test,12hr.sex.oral,12hr.sex.normal and now you're cross-posting a 
separate copy of your drivel to other unrelated groups again, like 
alt.alt.sex.  Guess it takes awhile to retype your post when one of 
your hands is constantly busy polishing the bishop.

Well, if they are monitoring YOUR particular traffic, it would be 
pretty easy for them to extract the NNTP commands while sniffing your 
traffic to see what groups you were visiting that generated all that 
traffic on your *personal* account with them.  Maybe they're just 
tired of having to deal with all the bandwidth consumption of 
masturbating binary group participants so the cure would be to simply 
deny the return traffic when attempting to visit the porn groups. 
That certainly would cut down on a large portion of their NNTP type
traffic.

They probably have gotten complaints from other users on your segment 
that they can't get any decent bandwidth - because you are sucking it 
all up.  Those other users didn't know it was you eating up all the 
bandwidth but just knew it got slow, they complained, and Comcast 
noticed the continuous high usage from your endpoint.  You don't want 
to share.  Their solution is to let others share and take out the hog. 
They have all their customers to consider, so getting rid of one bad 
customer is a no-brainer to maintain all the other accounts. 
Apparently you were warned before.  You chose to ignore the warning. 
So they decided to take action and you lost.

Go read their Acceptable Use Policy, section i.  You'll know the word 
that applies to you, then read section ii.  Then read section vii 
which applies to you sucking up too much bandwidth on the shared 
segment with other users on the same segment as you.  What, you 
thought Comcast wouldn't or couldn't censor your traffic?