Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat request: Track announces via autobrr/IRC for racing #29

Open
zakkarry opened this issue Oct 22, 2024 · 1 comment
Open

feat request: Track announces via autobrr/IRC for racing #29

zakkarry opened this issue Oct 22, 2024 · 1 comment

Comments

@zakkarry
Copy link
Contributor

zakkarry commented Oct 22, 2024

This is a continuation of a discussion that got a bit off-topic in a PR. I'm making this on behalf of @zivkovic to keep the discussion isolated from the PR.

See the first part here


In response to the last post....

I think the most effective and consistent way to implement this would be to use the {{.Artists}} macro, in tandem with maybe omegabrr to filter out the unnecessary announces (because much like with cross-seed, you will be hit with ALOT of music that is basically unnecessary, on the order of hundreds or thousands a day without filtering) - this can further be refined with format/quality settings in the filter itself. If setup incorrectly, especially if you're doing any comparisons that require snatching (I strong urge that you do not do this, as you know @moleculekayak that is pretty paramount to fertilizer and why cross-seed doesn't support music) you do so sparingly.

You should be able to - off the artist alone - get a list of potential candidates from the torrent directory that is rather slim, and narrow it down further off tokens such as format and quality to find potential candidates. There would be many ways to do this lookup. If you need ideas for this, although I don't think you would, let me know.

So basically the flow would be something like this, @zze0s may also have some input and potentially could help with some of this.

  1. Filter with format and quality you would expect to have + omegabrr artist filtering
  2. send {{.Artists}} and some other information without snatching the torrent - I suppose {{IndexerName}}, and a guid if you want
  3. lookup the artist locally for any torrents
  4. compare all candidates for matching criteria
  5. decide how to create or snatch the torrent if you find a match

The reason i say potentially you could match is, if this is done properly, there would be no hit or problem snatching a torrent you are almost certainly going to seed that I'm aware of, however if possible this could be done entirely locally in the same manner it is now.

@zivkovic
Copy link
Contributor

For now, as it is simpler, an action to run once a day(configurable) would be nice, to catch every not yet cross-seeded torrent and start cross seeding it, as you suggested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants