SSL encryption helps beat ISP traffic shaping!
Through Giganews' newsgroups and support lists we have seen that many ISPs have implemented traffic shaping measures over the last year to curb usage on their networks.
This is typically done at the protocol or port level. For example, if your ISP wanted to curb your newsgroup usage, they could say that any traffic being transferred over the NNTP protocol on port 119 cannot exceed 500 kilobits per second per customer.
In the past the best work around for this problem was switching to port 80 (typically used for HTTP), but if your ISP is filtering on the protocol level (all NNTP traffic for example) switching to port 80 would not do you any good. Your ISP might be looking for NNTP commands and limit your connection when it sees them.
This is where SSL comes in.
Because SSL is encrypting the authentication, header, article, and protocol data passed between your computer and Giganews any protocol-based filtering measures will be ineffective. The speed difference can be very dramatic. Many Giganews customers have already commented that downloading over SSL has made a huge improvement in their Usenet performance.
If you've recently experienced slow download speeds with any NNTP based downloading (Giganews or other) which you suspect is being caused by ISP traffic shaping, try out our new encrypted Usenet service to see if you can get around it.
Mitglieder in diesem Forum: 0 Mitglieder und 5 Gäste