-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
export const EP_REGEX = /^(?.+)[. ](?S\d+)(?E\d+)/i;
export const SEASON_REGEX =
/\^(?.+)\[. \](?<season>S\\d+)(?:\\s?-\\s?(?<seasonmax>S?\\d+))?(?!E\\d+)/i; </code></pre> <p>export const MOVIE_REGEX = </p> <pre><code>/\^(?<title>.+)\[. \]\[\[(\]?(?<year>\\d{4})\[)\\\]\]?(?!\[pi\])/i; </code></pre> <p>export const EXTENSIONS = ["mkv", "mp4", "avi"]; </p> <p>Other than that, there are several questions here, so I'll try to unpack them:</p> <p>Why not music, book, game, or software torrents?</p> <p>When I started the project, it was just a simple program that I wrote for myself and posted to GitHub. I made those choices because</p> <p>I have no experience with music, book, game, or software torrents. I also don't know if the naming schemes for non-video torrents are as standardized.</p> <p>Why not episodes?</p> <p>On most private trackers, episodes get deleted once a season ends and packs come out. I didn't (and still don't) see the point in cross-seeding episodes which would just increase the number of torrents I'd have to manually delete from my client at the end of a season.</p> <p>Why not nfos, subtitle files, posters, samples, rars, etc?</p> <p>Because I wanted to cover the 80% case that was easy and more likely to match across multiple trackers. When I created cross-seed, I made an assumption that video torrents with extra files would be less likely to match, so I decided to just filter them out entirely. I also wanted to be very conservative because cross-seeding is pretty heavy on trackers' APIs (and most trackers don't even have an api, they just get web-scraped, which makes it even heavier), so I only wanted to search for the torrents that would be the most likely to have matches. In my eyes, this is sufficient because cross-seeding is an optimization, and I consider any amount of cross-seeds to be a "bonus".</p> <p>The other reason is that I don't like when torrents have those extra files. IMO, all movie torrents should be a single file and all subtitles should be embedded. If cross-seed ever gets big enough that it can exert any sort of pressure on release groups to follow a more rigid pattern, I want it to urge people towards single-file movie torrents, no nfos, etc.</p> <p>I haven't given a lot of development to the other cases. I added the includeEpisodes and searchAll flags early on because they were easy to implement. At the time, I was also feeling very competitive towards <a href="https://github.com/BC44/Cross-Seed-AutoDL">https://github.com/BC44/Cross-Seed-AutoDL</a> so I wanted to make sure I had feature parity.</p> <p>will there be more inclusive options in the future such as allowing .nfo files, subtitles, and posters without having to use searchAll?</p> <p>Several people have asked for different prefilters for their use cases, so I created #210. I want to try to provide a solution along the lines of "easy things should be easy, hard things should be possible". My current idea is to allow people to provide a JS function inside their config file to filter. However, I don't plan on adding more specific options as I want to keep the defaults pretty opinionated, and I also want to avoid the proliferation of too many command-line options.</p> </div>
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a more popular project.