Sick-Beard icon indicating copy to clipboard operation
Sick-Beard copied to clipboard

The Pirate Bay Torrent Search Provider

Open AdrianRossouw opened this issue 13 years ago • 8 comments

This is a clean-up and re-rolling of an existing pull request by mr-orange. I removed all the unrelated changes, fixed white-space issues and squashed it into fewer commits.

I haven't tested it too much, but it seems to work as advertised.

The original description :

The Pirate Bay Torrent provider (NOT an RSS Provider), use some simple regex string to scrape data from TPB. The provider scrape the first 30 torrent ordered by seed per episode, it can filter torrent by trusted uploader (VIP, Trusted, Helper) if a flag is set in provider setting. It also use a web proxy to bypass some country blocking mechanism.

AdrianRossouw avatar Jan 03 '12 23:01 AdrianRossouw

thank you for your effort. I will close my request.

mr-orange avatar Jan 12 '12 08:01 mr-orange

Is still actually needed? Does SB work with magnet links?

http://torrentfreak.com/the-pirate-bay-will-stop-serving-torrents-120112/

flexd avatar Jan 14 '12 12:01 flexd

Any ETA on this one? Having TVDB problems with mr-orange's fork and would love to see this added here.

birarda avatar Jan 26 '12 05:01 birarda

Dunno about anyone else, but I started getting errors in my logs due to pulling down magnet links. I've since stripped the TPB provider from my fork. I haven't looked into the issue very deeply, but if TPB has finally stripped torrent links out of their RSS feeds, SB would have to be modified outside of the provider in order to handle magnet links (AFAICT).

I believe that currently once SB has chosen an episode to download, it determines whether it's an NZB or torrent and handles appropriately (with torrents, the only option is copying to a black hole directory). A third handler would need to be implemented for magnet links, and from there the options that come to mind are:

  • SB interprets the magnet link and retrieves the torrent information, creates a torrent file, and writes it to the torrent black hole directory. Not sure if this is at all doable, since I'm not an expert on magnet links.
  • SB tells the OS to open the link, using the default magnet-uri handler. Probably the most workable solution, though if you're running SB on a Linux machine, there might be configuration headaches. An override option could be provided that has the magnet link handler pass data to an external script (similar to how NZBs work in some setups).

Anyway, that's my take. Someone more familiar with SB's internals could probably estimate the feasibility of handling magnet links better than I.

cwc avatar Feb 02 '12 18:02 cwc

Hi Cameron i've updated my branch 2 week ago only for this type of Error Now the branch is Error free. I'm thinking To handle magnet link downloading the metadata from the swarm and rebuild torrent file . For the second approach i do not know if is possible with python.

Luca.

Il giorno 02/feb/2012, alle ore 19:10, Cameron Currie [email protected] ha scritto:

Dunno about anyone else, but I started getting errors in my logs due to pulling down magnet links. I've since stripped the TPB provider from my fork. I haven't looked into the issue very deeply, but if TPB has finally stripped torrent links out of their RSS feeds, SB would have to be modified outside of the provider in order to handle magnet links (AFAICT).

I believe that currently once SB has chosen an episode to download, it determines whether it's an NZB or torrent and handles appropriately (with torrents, the only option is copying to a black hole directory). A third handler would need to be implemented for magnet links, and from there the options that come to mind are:

  • SB interprets the magnet link and retrieves the torrent information, creates a torrent file, and writes it to the torrent black hole directory. Not sure if this is at all doable, since I'm not an expert on magnet links.
  • SB tells the OS to open the link, using the default magnet-uri handler. Probably the most workable solution, though if you're running SB on a Linux machine, there might be configuration headaches. An override option could be provided that has the magnet link handler pass data to an external script (similar to how NZBs work in some setups).

Anyway, that's my take. Someone more familiar with SB's internals could probably estimate the feasibility of handling magnet links better than I.


Reply to this email directly or view it on GitHub: https://github.com/midgetspy/Sick-Beard/pull/269#issuecomment-3783072

mr-orange avatar Feb 02 '12 18:02 mr-orange

Can torrent clients pick up magnet files from a watch folder and load them properly?

midgetspy avatar Feb 12 '12 20:02 midgetspy

No it's not possible at the moment.

Il giorno 12/feb/2012, alle ore 21:20, Nic Wolfe [email protected] ha scritto:

Can torrent clients pick up magnet files from a watch folder and load them properly?


Reply to this email directly or view it on GitHub: https://github.com/midgetspy/Sick-Beard/pull/269#issuecomment-3930664

mr-orange avatar Feb 12 '12 20:02 mr-orange

I've added magnet link handling to my fork (https://github.com/descention/Sick-Beard/commit/885e287d68620ad920e874b40a32cffcea13d4f8)

Magnet links can not be sent to a black hole, so an appropriate handler must be added. I added uTorrent for my setup.

Also, my apologies for the messy commit. I'm not sure how it chose to commit the whole file and not just the lines I changed.

descention avatar Sep 05 '12 17:09 descention