Very cool that you guys are thinking of this and care enough to try to work around the Bell stupidity, but in the end you'd probably spend a wad of cash on development and QA, only to realize Bell found a way to detect a pattern in your scrambling that identifies in, and patches the shaper or some other firewall for it.
said by velcomrob:I understand your concern Chrish and we are as much peeved off as anyone. I can only see one reason they're doing this, loss of customers.
We are working with several ISP's to try to come to a resolution on this matter as quickly as possible. We can't divulge to much information at this point (legal stuff).
But if worse comes to worse we will work very hard to find a way around this problem. First off Bell shouldn't be looking at our packets (data transfer) that occurs over our network. We have several scenarios we will pressure Bell. But in the end if they want to do child's play then be it. We ill possibly create some sort of application that sits on the clients side PC and that sits in the middle of our network that will scramble packets as they are sent to your side. The application will decompress the packet and thus rendering Bell's traffic shaper useless. I'm not 100% sure it can be done yet but we are investigating different possibilities. We are speaking to our developers about it.
The only limitation in this is data being transfered out to a recipient won't be encrypted. But your download speeds shouldn't be affected.
Let's hope its doable.
Again data being transferred our our network is private, so we will keep it private.
