mirror
/
Jackett
mirror of https://github.com/Jackett/Jackett
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated How to request a new tracker (markdown)

garfield69 2022-05-10 11:37:24 +12:00
parent a745a094fa
commit 5476f57474
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -12,10 +12,12 @@ 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) 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, 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#.
- If an API is not available, then as long as the site's results page is all HTML then yaml can be used.
- However, if the search page comprises results that are dynamically generated via calls to JavaScript functions, then C# will be needed.
- If the site supports an API:
- 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 very complex results that cannot be process with yaml, then we will need to resort to C#.
- If an API is not available:
- then as long as the site's results page is all HTML then yaml can be used.
- However, if the search page comprises results that are dynamically generated via calls to JavaScript functions, then C# will be needed.
- Yaml indexers are simple to write and maintain, and usually the turn around from request to implementation is fairly short.
- C# indexers do not have a quick turn around from request to implementation, due to the fact that C# developers are scarce and/or busy on other projects.