You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we need to update valid release years every decade. If we were to just allow any 20XX date, it would be fine if there are multiple years in the torrent name (usually true), but in the below example it wouldn't work:
Blade Runner 2049.HDRip.XviD.AC3-EVO
As it would parse 2049 as the release year. When we do reach the year 2049 though, there is no way to know whether it's a release year or part of the title, so we'd have to add it as a manual exception.
Regardless, maybe we look at system time in combination with a manual check. So, right now we allow 1900-2029 - maybe we allow up to 2029 OR current_system_year, so if we forget to update this library in 2030, it doesn't suddenly break. We also don't just depend on the system year as it might be wrong (super early, maybe), so we still keep the manual year.
The text was updated successfully, but these errors were encountered:
platelminto
changed the title
How to handle release years
Look at system time, together with manual limit, to check max possible release year
Nov 24, 2021
Currently, we need to update valid release years every decade. If we were to just allow any 20XX date, it would be fine if there are multiple years in the torrent name (usually true), but in the below example it wouldn't work:
Blade Runner 2049.HDRip.XviD.AC3-EVO
As it would parse 2049 as the release year. When we do reach the year 2049 though, there is no way to know whether it's a release year or part of the title, so we'd have to add it as a manual exception.
Regardless, maybe we look at system time in combination with a manual check. So, right now we allow 1900-2029 - maybe we allow up to 2029 OR
current_system_year
, so if we forget to update this library in 2030, it doesn't suddenly break. We also don't just depend on the system year as it might be wrong (super early, maybe), so we still keep the manual year.The text was updated successfully, but these errors were encountered: