So what to do? You have build up your own crowd of leechers downloading from you while you are still connected to the tracker of the private community. The connection to the tracker is necessary. It ensures that the external traffic - that means your uploads - count for your share ratio. The basic idea is to create a similar .torrent file and upload it to a public tracker as follows:
First you have to enhance the .torrent file you have downloaded from the community tracker web site. The crucial issue is that the infohash must not be changed. If it was changed, you have created a different resource and it will never work. Luckily the tracker URL information is not part of the infohash section of a .torrent file. To edit the .torrent file you have to export it in an .xml format. Azureus is an example of a bit torrent client that supports this export feature. The following example shows the enhancement of the announce URL tag:
http://community_tracker/announceis changed to
http://public_tracker/announce.
If you like you might create a public multi tracker .torrent file as follows or a variation of it:
http://public_tracker/announce
http://another_public_tracker/announce
http://public_tracker/announce
http://another_public_tracker/announce
But you might not want to insert your announce URL of the community tracker in this .torrent file you intent to publish on some public .torrent sites. So your community URL normally contains a passkey to identify your account. If you would publish it too, others might download on your ratio and that would probably ruin your ratio and your account. So your idea was to improve your ratio and not to ruin your account. A further bad issue is that in this case many peers would use your account from different IP addresses simultaneously. Many trackers then refuse to connect. As told before, the infohash section has to remain unchanged. It is:
7B75007BC793DEF….C1332B4C88A9C4C6Aand
alotofdetailsYou then re-import the enhanced .torrent in .xml format to the conventional bencoded format. Now you have a fully functional .torrent file with the same infohash value. If the .torrent file initially was a private one it is now still a private one. Unfortunately the “private” information is inside the infohash section. See it in your .xml file. To produce a public .torrent file would result in a different resource that is no more compatible to the resource you originally received from your community tracker. Even if the content like software or music is still the same.
You upload this enhanced .torrent file to one or more public .torrent communities or .torrent file listing sites. I don’t give recommendations which one you like to prefer. Users of those public sites will download your .torrent file and start the .torrent.
To be continued in next part