Torrent cloud search provider specification

search-example.json

{
	"mininova": {
		"name": "Mininova",
		"type": "screen-scraper",
		"list": {
			"url": "http://www.mininova.org/search/{query}/seeds/{page}",
			"items": ".maintable > tr",
			"item": {
				"name":"td:nth-child(3) > a:nth-child(2)",
				"url":"td:nth-child(3) > a:nth-child(2)@href",
				"size": "td:nth-child(4)",
				"seeds": "td:nth-child(5)",
				"peers": "td:nth-child(6)"
			}
		},
		"item": {
			"magnet": "#download a:nth-child(3)@href"
		}
	}
}

torrent-cloud-search-provider-spec.md

Torrent cloud search provider specification

Search providers are simply a JSON object with each provider as the keys. There are currently two types of search providers: screen-scrape and json-api:

screen-scrape

Here is an outline screen-scrape configuration file, where the dynamic values are documented between the < and >:

{
	"<search provider id>": {
		"name": <displayed name>,
		"type": <either "screen-scape" or "json-api">,
		"list": {
			"url": <search url with placeholders for the search query and page number>,
			"items": <selector to the all result items>,
			"item": <within the context of each item> {
				"name": <selector to the item name>,
				"url": <selector to the item url>,
				"seeds": <selector to the item seeds integer>,
				"peers": <selector to the item peers integer>,
				"magnet": <selector to the item magnet>
			}
		},
		"item": <after following the item's url> {
			"magnet": <selector to the item magnet>,
			"infohash": <selector to the item infohash (infohash+tracker = magnet)>,
			"tracker": <selector to the item main tracker (infohash+tracker = magnet)>
		}
	}
}

By default, all of the selectors above, will use the result element's text value. If you wan't to use the value of an attribute instead suffix your selector with @<attribute name>. If a Regular Expression is more convienient than CSS selector you can use /<regex>/, though note, since \ is a JavaScript string escape character, you'll have to escape it first – so \ all become \\.

In list.url you must include the placeholders {query} and {page}, when you perform a search page is set to 1 and will incremenet as you use the "Load More" button. For search pages which are zero-indexed, use {zpage} instead.

If magnet is not defined in list.magnet then a follow up item query will be required, where you may use magnet or the magnet URI can be infered with infohash and tracker.

See above for a Mininova example (hosts copywrite-free torrents). You can use it with:

SEARCH_PROVIDERS_URL = https://gist.githubusercontent.com/jpillora/e667f3d16a6bd403edc4/raw/af4ff4a66a1599ccfd6940d90c633a39ecbf6ba1/torrent-cloud-search-provider-example.json

json-api

In progress

A few more here http://pastebin.com/raw.php?i=bVvK6rba

Here are a few more providers: http://pastebin.com/raw.php?i=bVvK6rba

SEARCH_PROVIDERS_URL = http://pastebin.com/raw.php?i=bVvK6rba

Here are a few more providers: http://pastebin.com/raw.php?i=fLxJmHSv

SEARCH_PROVIDERS_URL = http://pastebin.com/raw.php?i=fLxJmHSv