This is just a webpage, and since Drupal is a CMS, that's not a problem. The tracker listing of all currently available torrents (the visual part of a tracker) is the part most of us only know. It's important for the tracker to honor the access rights of the corresponding node.
Of course, there should be a torrent tracker which conforms to the BitTorrent 1.0 protocol as written here. The module should store its torrents as a CCK field - it's advised to start with the existing filefield module and build on it. Also many communities are built around a BitTorrent tracker, why not let them benefit from Drupal's possibilities? Deliverables More and more sites provide large downloads, and BitTorrent is the best way to distribute those files. The need for a good BitTorrent tracker for Drupal is obvious. This means you will have something to start from, or at least something you can learn from. Now there are plenty perfectly legal use cases, so that fear is now obsolete, and that's why he contacted me.
Users who contacted me: hugomelo (on March 25), bradfordcp (on March 19), CitizenKane (on March 1).Īlso I've been contacted by the original BitTorrent Tracker module for Drupal 4.6, which wasn't released to the public, out of fear for abuse back then. If somebody would like to continue with this proposal, and I'm sure somebody will because I've already been contacted three times about this proposal, the SoC mentors may decide whom is the best candidate.
Originally I intended this as my own project proposal, but - unexpectedly - I was given the opportunity for working on a new startup, which is of course even better than SoC.