Updated How to request a new tracker (markdown)

garfield69 2022-05-09 06:31:07 +12:00
parent 4b1276e762
commit 002f65e59a
1 changed files with 1 additions and 1 deletions

@ -8,7 +8,7 @@ If the site has open registration then include this info in the ticket.
- Sites that only provide direct downloads to browser, or direct play/view, or redirection links to file storage sites or paywall services, are not suitable for use with Jackett.
- If the site has one title for each torrent/magnet on the search results page, then we can usually code an indexer in yaml using the Cardigann processor.
- If the site has multiple torrents/magnets under one title, then as long as these are on the primary search page, then the indexer can be coded in C#.
- However, if the search page only holds a list of titles, and the multiple torrent/magnets are on a corresponding details page, then these sites are not suitable for indexing. This is because to complete the torrent search results, Jackett would need to potentially make up to 100 additional http GET requests to the site, one for every title in the search results page, and no site is going to want that kind of bulk traffic.
- However, if the search page only holds a list of titles, and the multiple torrent/magnets are on a corresponding details page, then these sites are not suitable for indexing. This is because to complete the torrent search results, Jackett would need to potentially make up to 100 additional http GET requests to the site, one for every title in the search results page, and no site is going to want that kind of bulk traffic, a quick way to get your IP banned for bot activity if also teamed with automation software like Sonarr or Radarr.
- If the site uses an API that returns JSON or XML then in most cases we can write the indexer in yaml.
- The use of an API is preferred over the other method, HTML scraping.
- If an API is not available, then as long as the results page is all HTML then yaml can be used.