Updated How to request a new tracker (markdown)

garfield69 2022-05-09 14:46:31 +12:00
parent f984db3b4d
commit a745a094fa
1 changed files with 1 additions and 1 deletions

@ -11,7 +11,7 @@ So please, get an invite and be ready to invite the staff member who will implem
- On the site's search results page:
- 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#.
- 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, its a quick way to get your IP banned for bot activity, espicially if teamed with automation software like Sonarr or Radarr.
- 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, its a quick way to get your IP banned for bot activity, especially if teamed with automation software like Sonarr or Radarr.
- If the site supports an API then this is preferred over the other method, HTML scraping.
- If the site uses an API that returns JSON or XML then in most cases we can write the indexer in yaml.
- If the JSON/XML API returns very complex results that cannot be process with yaml, then we will need to resort to C#.