* Add codec and medium filters to HDBits API
* Add checkboxes support to CardigannIndexer
* Expose multi-select as template variable
* update datestamp to force cache refresh
Co-authored-by: garfield69 <garfield69@outlook.com>
* Create Nordicbits.cs
Add support for Nordicbits / DK Private Tracker
* Create ConfigurationDataNordicbits.cs
Create Nordicbits.cs
Add support for Nordicbits / DK Private Tracker
* Update README.md
Added a new tracker Nordicbits
* Update Nordicbits.cs
The self-tester didn't work, because of the trackers use of 'Today' and 'Yesterday' in releases. Where other releases are "MMM dd yyyy".
This is fixed now.
* Update Nordicbits.cs
Search string wasn't build proberly, due to the catagory of nordicbits.
The images, which we use to determin which catagory the release is from goes like this -
cat=5
But when we need to search under that catagory and have more than one, it should go like this -
cats2[]=5
Changed the categorieslist, by using replace and changed the query string to match the original search string.
* Update Nordicbits.cs
Should solve the bug - The string was not recognized as a valid DateTime. There is an unknown word starting at index 0.
* Update Nordicbits.cs
Tracker don't support imdb, therefore problems with handling of couchpotato, radarr or similar.
Fixed by setting imdb to false;
* Add option for Elite Tracker (FR) for download torrent using https for tracker URL.
* change return type.
clean code.
* use the SiteLink variable instead of hard coding
Really hope I don't break anything with this
Went to have a go at .NET core and it just became too confusing for me with 'Jackett' namespace referring to both Jackett.Common and Jackett
* Use platform detection that works on mono 4.6+
* Move to use package reference for restoring nuget packages.
* DateTimeRoutines does not have Nuget packages that support .NET Standard (and therefore .NET Core). We will have to include them for now until we can get rid of this dependency.
* Start spliting some interfaces into their own files - this will help by allowing us to split them out in the future into a seperate project so the actual implementations can stay within their respective architectures when required
* Move out common libraries
* Few more tidy up tasks to get things working with .NET Standard
* Restructure the solution layout
* Encoding work to reduce rework later on platforms without Windows codepages (or require compliance with RFC1345)
* Move folder structure around to have more natural layout of the solutions
* DI server configuration to get rid of "temporary" hack and dependency circle for serverservice
* Make all encoding consistent to match the expected encoding casing for earlier versions of mono.
Diego Heras