The torrent client crashed about 12 hours ago, so any downloads started during this period will have failed to start. I have restarted the client and all torrents are now downloading. Apologies for the inconvenience guys.
bytesized hosting has the following rule:
We do not allow the use of torrents that are registered on a tracker that allows anyone to sign up without an invite. The rule of thumb is: If you can get a .torrent file of the server without an invitation, then the tracker is banned. This policy is enforced through our firewall as well as scanning for torrent files containing trackers that are publicly accessible. [...]
I did not notice this rule. Thanks for pointing it out. I was considering using this service but I guess that's out of the question now.
Would it be too difficult to ensmarten the bandwidth throttling rules?
...
The short answer is yes. Because I would have no idea how to go about doing it.
Your speed issues (1mb transfer limit per connection) are however probably not being caused by unfair use of the severs bandwidth. I can download from this server at high, unthrottled speeds here in europe. But I have heard otherwise from some US users. The server is on a 100mbit dedicated line located in Luxembourg and is capable of speeds up to 10mb/s.
I suggest you use a download manager to control the number of connections to the server. I suggest using 5 parallel connections if you are having difficulties with per-connection speed limits.
This has been a problem since the launch of this service (see the first 2 pages of this thread where we discussed this). I get only around 200 to 300 kB/s per download thread (on my 100mbit downstream link) which I'm able to scale up linearly by using 10 or even more parallel threads (axel is my friend!). But I don't think these are mjcmurfy's throttling rules either. This probably comes from some ISP/router along the way when routing packets to certain hosts. mjcmurfy says that he's able to get pretty high, unthrottled speeds in his own testing:
...
It's a pity that this is a problem for a website dealing in downloads. It would be fantastic if this could be investigated (I offer to be a testing guinea pig if needed!)
I don't have much control over what is causing this problem really. This would seem to be an issue with particular ISPs somewhere along the route. The only way to solve it probably is to purchase another server with better connectivity I think. The current server arrangement however is quite favorable for me and the server is nowhere near it's limit in terms of maximum concurrent bandwidth use.
I'm not really an expert in this level of network spelunking, but I will do my best to look further into this situation and appreciate any suggestions you or anyone else might have.