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
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.
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.
Filter with format and quality you would expect to have + omegabrr artist filtering
send {{.Artists}} and some other information without snatching the torrent - I suppose {{IndexerName}}, and a guid if you want
lookup the artist locally for any torrents
compare all candidates for matching criteria
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.
The text was updated successfully, but these errors were encountered:
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.
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.
{{.Artists}}
and some other information without snatching the torrent - I suppose{{IndexerName}}
, and aguid
if you wantThe 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.
The text was updated successfully, but these errors were encountered: