BoundSyco Posted October 9, 2006 Report Share Posted October 9, 2006 A while ago I wanted to write a tracker just for the hell of it, so I did. When I wrote it, I implemented it the way I thought trackers should be implemented, of course, this doesn't mean that anyone else implements them this way. Most trackers, that I know of, classify themselves as either 'Open' or 'Closed' trackers. Open trackers are those which allow anyone to use them without registration. Closed trackers require registration.Both varieties of trackers (as far as I know) require that the torrent must be registered with the tracker before the tracker will acknowledge it and track peers for it. The reason for this, as I see it, is to have some sembalence of control over how much bandwidth gets used. This also has the nice benifit that a majority of these trackers also supply a very easy way to find everything that it tracks.However, in my opinion, the tracker shouldn't be responsible for keeping track of the torrent files. Sure, you can have an integrated service, but they should be seperate entities. I also believe that trackers should track anything that a client points at it. There would be no "registered" torrents for the tracker, and no way to actually know what is being tracked. (This doesn't mean that torrents cannot be banned if a torrent is used for sharing data you do not want widely distributed)I don't really know if this is a good idea or not, but I would like some feedback.You can test the tracker by pointing any torrent at:http://www.wetspunk.net/announce.phpYou can check the source code and such here:http://www.wetspunk.net/Forums:http://www.wetspunk.net/forums/ Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.