mirror/Jackett
1
0
Fork 0
mirror of https://github.com/Jackett/Jackett synced 2024-12-22 15:57:50 +00:00
Code Issues Releases Wiki Activity

Updated How to request a new tracker (markdown)

garfield69 2024-12-03 15:20:33 +13:00
parent 0bb2c22c80
commit dbc42ab9d8
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
How-to-request-a-new-tracker.md

@ -22,7 +22,7 @@ So please, get an invite and be ready to invite the staff member who will implem
- If there are titles (or posters) for each torrent/magnet, then we can usually code an indexer in yaml using the Cardigann processor. - If there are titles (or posters) for each torrent/magnet, then we can usually code an indexer in yaml using the Cardigann processor.
- If there are titles (or posters) with groups of related torrents/magnets, then the indexer can usually be coded in C#. - If there are titles (or posters) with groups of related torrents/magnets, then the indexer can usually be coded in C#.
- However, if there are only titles (or posters), and you have to navigate to the corresponding details page to find the multiple torrent/magnets, then these sites are not suitable for indexing. This is because for the indexer to complete the torrent search results, Jackett would need to fetch the details page for every title in the search results page, (potentially up to 100 pages), and no site is going to want that kind of bulk traffic, it's a quick way to get your IP banned for bot activity, especially if teamed with automation software like Sonarr or Radarr which can make many search requests in a short time with frequency until satisfied. - However, if there are only titles (or posters), and you have to navigate to the corresponding details page to find the multiple torrent/magnets, then these sites are not suitable for indexing. This is because for the indexer to complete the torrent search results, Jackett would need to fetch the details page for every title in the search results page, (potentially up to 100 pages), and no site is going to want that kind of bulk traffic, it's a quick way to get your IP banned for bot activity, especially if teamed with automation software like Sonarr or Radarr which can make many search requests in a short time with frequency until satisfied.
Even if we add a request Delay between Gets of say 1 second, it would add up to 101 seconds (assuming the site responded in a timely manner to all requests) before results become available, which is getting close to the maximum timeout after which the Indexer would give up waiting. Even if we add a request Delay between HTTP GETs of say 1 second, it would add up to 101 seconds (assuming the site responded in a timely manner to all requests) before results become available, which is getting close to the maximum timeout after which the Indexer would give up waiting.
- If the site supports an API: - If the site supports an API:
- then this is preferred over the other method, HTML scraping. - then this is preferred over the other method, HTML scraping.
- If the API returns JSON or XML then in most cases we can write the indexer in yaml. - If the API returns JSON or XML then in most cases we can write the indexer in yaml.