I am part of the Podmailing team, a software based on BitTorrent. We are organizing a release test of a new solution to bypass BitTorrent throttling, thanks to a hybrid BitTorrent / http protocol.
If you suffer from BitTorrent traffic shaping from your ISP, we need your help to validate our solution in as many cases as possible and to finalize our implementation.
Deluge is already pretty good at evading throttling.
On the other hand, I never got why all of the major torrent client makers didn't simply adopt the RST flag firewall approach and incorporate them in a mandatory update, I mean, if everyone has it in their clients, then it works, right? The argument was that everyone had to do it, all that was needed to have been done was to do it for everyone in a mandatory update where the client ignores the fake RSTs...
Not all of the torrent programs would do it though... and we'd be stuck with clients that have and clients that have not.
Only foreseeable option I think is to have it be coded as an optional feature in all clients, then once all clients have it capable, then tell everyone to enable it at once. I just don't think it would ever happen though.
A while back in the forum wasn't there something libtorrent was working on implementing that verified bypassing Comcast sandvine anyway?
First time/post here. Here because of Comcast......
I always thought about something similar to this. Like emailing .torrent files to each other if the P2P landscape got too bad. But, isnt this what got the original Napster in trouble? I think it would be an easy way to get the server shutdown if "other" folks found out.
Deluge
.
