Port Bittorrent Module to D6

Currently I have a big patch I want to roll out taking the BT module in RC status. After that I will look into doing the port to D6. I will have time to finish up that patch and begin a port later on this month. Thanks for your interest!

subscribing

Subscribing. Any updates on this? ETA?

Regards,

Dennis

bump, subscribing, can't wait and available for testing.

Hi. Port this module, please, on D6. I with pleasure will use the module, but now my site is transferred on 6, and the module still for 5 versions. I am sorry for clumsy English, the program translated.

Wow there is a lot of activity here. Time permitting I will try and close out some of the major bugs for version 5 and perform the beginning steps on porting to 6 this weekend.

ok, I will wait very much. Thanks for the operative answer! :)

Is anyone working on this?

it seems no one is working on a port: (

Hello when will you port this module to drupal6??????????

I am looking into porting this to d6 at the same time as applying some updates.

Hello,
Thanks for your work bradfordcp. Have you got news about the port on Drupal 6 ?

I could be very interrested to testing your module, because I'm co-admin on a free french bittorrent tracker (free softwares, CC music and videos...), and we're looking for to upgrade the actual tracker to a portal about free culture. I would like to propose Drupal to my team. And I'm using Drupal 6.x on another projects :-(
Thank you for your reply.

Best regards.

Subscribing

helo

Im also very interested in that port, is there any progress ?

cheers !

I want to help building Port to D6 so I am sending Logo Design for module.
Logo of bittorrent module is here

me too dying for D6 port.

I offer few hours of video montage for the one who port it to 6.0 and solve main bugs.

yes yes, the hero who do that, might send me dv tape (or .dv files via bittorrent) and i cut it into a semi pro movie and send back dvd image.
no joke ;)

Its really important module, all the other floss trackers are crap like a early phpnuke ...

Alright, the D6 port is underway, I have set aside the time and shuffled around projects to get down to business. Here is the list I am looking at right now:

1. Bring over the menu function from D5 and convert to D6 structure. This involves creating separate files for various aspects of the module as a lot of the code that will be used takes a lot of space and navigating a huge file like that again is not on my to do list :)
2. Work with tweaking how torrents are submitted / uploaded - D5's upload was a pain, but I have a lot more experience with the D6 uploader / form.
3. Add in the ability to upload file and have them web seeded
4. Add a location for the user to manage their torrents (should this be a tab on the user page or a view?)
5. Get back into the tracker code and update some of its logic (it needs a little bit of an overhaul)
6. Clean-up BitTornado web seeding implementation and test accordingly.
7. Expand BitTornado web-seeding options - This protocol allows for greater control over who can access what and how often. The only issue is that it must run within PHP (even the byte retrieval).
8. Create new Views functions - The views implementation in the last module is a little sloppy and could definitely use some improvements. I am doing this last as most of the information will already be in the node object, this just adds functionality.

Thank you for your support, I understand that I have been slacking. The main improvements to the module will be happening here and then backported to D5. Get your feature requests in now!

~Chris

Update: The torrent node type port is going well, I hope to have it finished shortly. I believe there may be a slight hiccup with respect to views, but I will look at that when the time comes. For now I hope to have that portion ported over by the end of the week.

UPDATE: The torrent node type is humming along nicely. Web seeding has been removed from the basic torrent node type and will most likely be implemented in a new different node type. I have revamped how torrents are submitted to alleviate issues where only one file could be attached to the node. Now the module will only accept one .torrent file attached to it. Other than that it doesn't care what else is attached to the node.

I know its really hard to redesign the code again.
But here is scenario where the torrents are so large that they have to be broken into several parts so that every user don't have any problems with their connection speed.
BY attaching several torrent files to one node, it would be much better to manage rather creating a new node and attaching the second part of torrent.

This would not be that hard to implement, but my priority is getting a near one to one port in place. Feel free to create an issue under the feature request category and I will update that when it is implemented.

Hi I wonder if the web-seeding works? or must I wait

I want to say it worked in D5, but I am a little hesitant as I have been reviewing previous code. The D6 version will support web seeding. Now if it will be working by the time the module is first released for D6, that is a definite no. The order of precedence is as follows:

1. Torrent Node Type DONE
2. Torrent Tracker In Progress
3. Release Base D6 Port
4. Implement Web Seeding
5. Implement Upload based torrent generation

Where are we with the D6 Port?

The short answer: Testing! I think I have successfully cleaned up a bunch of issues within announce.php. There are still a few I know are in there. I am testing locally, but I will also perform a CVS commit so those brave souls who want to give it a shot can. If you find any issues please create NEWNOT have web seeding. That has been stripped out and will be placed in a separate module along with converting uploaded files into torrents. Thanks for the help and I look forward to a fully stable release in the very near future.

Due to issues with how binary information is sent, clients not sending data in the way the specs describe and PHP being finicky with binary strings. I am reworking the information hash, peer_id, and key in hex format instead of blob.

Base port is successfully tracking torrents on the site with public scope, no passkeys, and without web seeding. Steps to reach beta status:

1. Verify scrape is working correctly
2. Bring passkeys back into the tracker
3. Verify that the various scopes and tracker controls are working correctly

Items that will not make the base port (but will be implemented once a stable tracker is released):

• Views 2 integration
• Web seeding - I know that this is very important and i would like it to be in there, but it requires a LOT of careful testing. It will be one of the first items to be re-implemented
• Multiple torrent files attached to a single torrent node
• Automatic torrent generation of uploaded files

Please feel free to place issues in the queue while testing. Also note that I made the commit shortly after midnight, if you are testing with code pulled through CVS kudos, feel free to submit bugs. If you are pulling the module from the releases page, please note that these files are generated twice daily and may not be entirely up to date.

Scrape should be working now, I had to overhaul quite a bit of the code as it required on certain fields being BLOBS. The commit last night had quite a few database updates so anyone running this version will need to uninstall and reinstall to get the changes (sorry for the lack of hook_update methods, but that would be a hassle while developing at this pace). Also scraping other trackers through CRON should work now as well. I have implemented this for users who do not want to track, just host the torrents.

Please start testing with the BETA 1 release. Once all of the bugs are out of this release work will begin on adding features back into the module. Please create new issues against the new code release.