From 6372a99f980adcb992a0d3c8d26bea3c305bfe8d Mon Sep 17 00:00:00 2001 From: garfield69 Date: Sun, 24 Apr 2022 18:13:08 +1200 Subject: [PATCH] Updated How to request a new tracker (markdown) --- How-to-request-a-new-tracker.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/How-to-request-a-new-tracker.md b/How-to-request-a-new-tracker.md index b910cf7..94ce144 100644 --- a/How-to-request-a-new-tracker.md +++ b/How-to-request-a-new-tracker.md @@ -6,8 +6,8 @@ So please, get an invite and be ready to invite the staff member who will implem If the site has open registration then include this info in the ticket. - The site must provide .torrent or magnet or both. Sites that only provide direct downloads to browser, or direct play/view, or redirection links to file storage sites are not suitable for use with Jackett. - If the site has one title for each torrent/magnet then we can usually code an indexer in yaml using the Cardigann processor. -- If the site uses an API that returns JSON then in most cases we can also write the indexer in yaml. +- If the site uses an API that returns JSON or XML then in most cases we can also write the indexer in yaml. - Yaml indexers are simple to write and maintain, and usually the turn around from request to implementation is fairly short. - If the site has multiple torrents/magnets under one title, then the indexer will need to be coded in C#. -- And if the JSON api returns very complex results that cannot be process with yaml, then we will need to resort to C#. -- C# indexers do not have a quick turn around from request to implementation, usually due to the fact that C# developers are scarce or busy on other projects. +- And if the JSON/XML api returns very complex results that cannot be process with yaml, then we will need to resort to C#. +- 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.