Slashdot Mirror

That's what I finally had to do, when some entity (might've been download.com, might've been someone else) offered an alternative download location for my software - which bundled some sort of malware installer onto my software. After one attempt to remove them as an alternate, I was told I could request my software be removed, and that's what I did. This occurred back in 2004.

Ah, found the answer, thanks AC. Unfortunately Ubuntu put the torrent files on their releases server, which is slow. Here are mirrors:

ubuntu-8.10-desktop-i386.iso.torrent
ubuntu-8.10-desktop-amd64.iso.torrent

Ah, found the answer, thanks AC. Unfortunately Ubuntu put the torrent files on their releases server, which is slow. Here are mirrors:

ubuntu-8.10-desktop-i386.iso.torrent
ubuntu-8.10-desktop-amd64.iso.torrent

BitTorrent download

Ports aren't really the problem. If you don't forward ports, other people can't initiate connections with you - you can only initiate connections to others. That's just the way NAT and port forwarding work. If you and another guy both have port forwarding disabled, neither of you can connect to the other. If either of you have port forwarding configured, the other one can initiate the connection and sharing can commence. If you only have 10 people in the swarm, cutting out half the people due to a lack of port forwarding will severely impact your download rates. However, cutting out half of the millions of WoW players still leaves over a million other users to connect to, which should be plenty to max out your download. See http://bt.degreez.net/firewalled.html and http://userpages.umbc.edu/~hamilton/btclientconfig.html for more info.

This is the real problem. Blizzard's BT client has very poor or no upload control. While downloading a file, a connection occasionally reports its status back to the sender, letting it know to keep sending data (in greatly simplified terms). If you're saturating your upload channel, your download can't report back that it's good for more data - the upload chokes off the download. It's very common with improperly configured BT clients, but can show up anytime you're uploading something (for example, unchecked uploading via FTP).

I can verify the other poster's claim. I watched as the Blizzard patcher saturated my upload and downloaded at <2K. Using an external app, I limited the patcher's upload to about 3K less than what it had been using. With no other changes, the patcher took off and maxed out my download speed.

Solution? Extract the .torrent file from the patcher and download it with your regular BT client. CapnBry's WoW Torrent Extract will easily extract it for you, and I post them as soon as I can at http://gaming.invisibill.net.nyud.net/wow/torrents/.

You mean like this one?

That's what a BitTorrent link is for.

http://degreez.net/Batman_Net.mov.torrent

Sorry, that torrrent file is slashdotted. Is there such a thing as a BitTorrent download of a torrent file?

Just curious, try this torrent instead...

http://degreez.net/Batman_Net.mov.torrent, courtesy of TheSHADOW.

Please help seed.

n/m I was able to download the file and put up a torrent myself.

http://degreez.net/Batman_Net.mov.torrent

Torrent: http://tracker.degreez.net/downloads/1984macintro. mov.torrent

http://tracker.degreez.net/downloads/1984macintro. mov.torrent

The reason why the "extra long tail" is so amazingly long is because the authors are merging two different types of BitTorrent usage. BitTorrent was designed for legitimate content, and for content distributors to run their own trackers. For example, my tracker is used just to distribute my own projects. Distribution is off the main website, with only one torrent shown. This is an example of BT's legitimate use, and even the largest legitimate BitTorrent sites pale in comparison to the piracy sites. There, you'll see much higher numbers of torrents, and few servers that only distribute small numbers of torrents.

I am the lead coder of a BitTorrent client. A few months back I began to receive reports of ISPs either blocking or severely throttling the upstream (to a point where the protocol became non-functional) of BitTorrent connections. As a result, I modified my codebase to by default choose a server port randomly, rather than within the default BitTorrent port range.

Lately, I've gotten more reports indicating that these ISPs that have been blocking BitTorrent have been using more sophisticated methods of detecting the protocol, by apparently sniffing the initial protocol handshake.

My response was this letter. The next iteration of the BitTorrent protocol is already being planned, and if this sort of behavior spreads, the new protocol's handshake will be made nearly impossible to sniff out. Yes, it's true BitTorrent is being misused for trading pirated content, but it's also being used for good purposes, such as publishing Linux distros, and in some cases it is practically impossible to obtain content without doing so via BitTorrent.

This will of course make it difficult to meter how much network traffic is being used by BitTorrent, or to throttle it moderately, but the purpose of BitTorrent is to distribute content, and all other concerns come second.

SpaceShipOne-large.torrent

Not my tracker. This contains documentary-style footage of the launch.

Download video via BitTorrent at X-Prize-flight-1.wmv.torrent

"Try disconnecting your router and connecting your computer straight to your uplink." on his forum.

If that works, here is the explanation as to why: "Some routers have been implicated in consistently corrupting data inside TCP packets, either when running in game mode or simply due to lousy firmware coding. They'll replace any instance of the external IP to the internal one for incoming data, and vice-versa for outgoing."

"Try disconnecting your router and connecting your computer straight to your uplink." on his forum.

If that works, here is the explanation as to why: "Some routers have been implicated in consistently corrupting data inside TCP packets, either when running in game mode or simply due to lousy firmware coding. They'll replace any instance of the external IP to the internal one for incoming data, and vice-versa for outgoing."

And I do. For those not in the know, Azureus is an open source Java BT client. It has its share of problems, most of them coming from its Java heritage, but it looks pretty and offers a lot more functionality than the vanilla BT client. If you want most of Azureus' features but don't care about the GUI, you may also want to try out Shadow's BT Client. It looks basically like the vanilla client.

Frankly, Bittorrent++'s GUI is too slow for my taste, and I don't think it's based on the latest BT protocol. These are BT clients I recommend:

• Azureus (the best in general)
• BitComet (limit to 1 port, for minimal internet browsing slowdown. But that prob. is why it doesn't have to fastest download performance, although you may have good mileage with a bit of tweaking)
• TheShadow's (one of the oldest "experimental" implementation, a mod of the official BT client with useful featrues)

The multitracker spec has already been implemented in many of the better bittorrent clients.

--

This method has resulted in much higher seeding efficiencies, by both inducing
peers into taking only the rarest data, reducing the amount of redundant data sent,
and limiting the amount of data sent to peers which do not contribute to the swarm.
Prior to this, a seed might have to upload 150% to 200% of the total size of a
torrent before other clients became seeds. However, a large torrent seeded with a
single client running in super-seed mode was able to do so after only uploading
105% of the data. This is 150-200% more efficient than when using a standard seed.

Put those .torrent files somewhere safe (so you can resume the download if necessary) Then run them through the Official Bittorrent

But I recommend this particular client.

You need to download a bittorrent p2p program that uses the .torrent file to start downloading.

Not that any of this matters, since BitTorrent is blocked on my network connection. *grumbles*

So change the port by trying this client. Everyone should change the port that bittorrent listens on, if everyone did, then ISPs couldn't easily block it. If they block incoming ports 6881-9 or whatever then it still might be blocked, but if someone else is on the torrent that changed their default port, then you still should be able to use it, although not as quickly.

Available here. Someone please mirror this torrent, uploadit.org probably can't host it for too long.

Torrent is built with backup trackers, so if you're using TheSHAD0W's experimental client it will fall-back to the next tracker in line if one is down.

I prefer Shadow's BitTorrent client on *nix (where the browser mime/file association isn't automatic).

--

I feel for you if you're still using the official client. It has NO features compared to burst or Shad0w's client. And they've had all the code changes in 3.3 for a long time now since they track CVS. Dump that stock shit.