Updated General guidelines for what an Indexer should aim to provide (markdown)

garfield69 2021-10-28 20:12:28 +13:00
parent ca061f4e12
commit 4c36014f49
1 changed files with 1 additions and 1 deletions

@ -2,7 +2,7 @@ Whether you are coding an Indexer in yaml or in C#, these are some general guide
- The indexer should be able to return results for torznab apps that will make queries by movie titles or TV episodes, etc. If the site cannot deliver search results from across their whole database then there is little point proceeding.
- The secondary function of an indexer is to respond to a keywordless query, by providing the most recent torrents added to the site (up to the first 100).
- Only direct .torrent downloads or magnets URI should be provided. Sites that use 3rd party filesharing services, or anything that provides intermediate pages (with timers or click me to proceed, or other manual interventions) before returning the download link should not be supported. This excludes requests for thank you before downloads, which are catered for by the standard indexer support modules.
- Only direct .torrent download links or magnet URI should be provided. Sites that use 3rd party filesharing services, or direct play links, or anything that provides intermediate pages (with timers or click me to proceed, or other manual interventions) before returning the download link should not be supported. This excludes requests for thank you before downloads, which are catered for by the standard indexer support modules.
- Generally we aim to provide a max of 100 torrents per query as most torznab apps ignore additional torrents above this max anyway.
- If possible, the query to the web site should include a sort request, the default being sorted by the added date, with optional sorting available for title/name, seeders, and size. But its not a problem if there is no sorting available.
- Poster links are a great addition to the response, and if no poster is available a null value is usual.