Could you please provide sample how to configure rutracker with magnet?

Thanks @liiight for the review, I updated my PR with all your suggestions, and also added more features:

• multi tracker (they seem to randomly generate one in 4, I generate all 4 (easier for the test, maybe I should random the order and/or follow what upstream does: send only one, but it seems less robust, but then tests are harder to do..))
• topic title as Display Name in magnet uri, hoping it would help with some clients when magnetization timeouts.

If you have time, could you please reply to my questions in my initial comment? Thanks !

@githubbla It should work using their forum rss/atom feed: http://feed.rutracker.cc/atom/f/0.atom

If you also want music parsing I have a somewhat working version 0 there: https://github.com/Niluge-KiWi/Flexget/tree/dev-music
(usage: filter previous atom feed with an artist list)

@liiight If you have time, could you please reply to my questions in my initial comment? Thanks !

@Niluge-KiWi I'll try to respond ASAP

@liiight last round of requested changes done!

Side note: most of your (valid) remarks also apply to other files in sites/*.py (notably site_1337.py), it's thus confusing from an external contributor: I mimic what I see in the project, notably I tried to validate with flake8 initially (as documented there https://flexget.readthedocs.io/en/latest/develop/index.html#code-style) but got many errors running it on sites/*.py, so I concluded it's not enforced in the CI/mandatory. Maybe cleaning these and enforcing more things in flake8/pep8/other checker if needed could remove this manual back and forth for 4 months. I do understand it would take time. But once it's enforced by CI checks it won't diverge again: it's a one-time cost. I could help if needed (autopep8/yapf hopefully can lift most of the work).
It would give you more time to answer deeper questions about code architecture than coding style.

@Niluge-KiWi thank you for your contribution!
You are absolutely right about the formatting issue. We do use pre-commit which runs black manually, I guess we should maybe just add it as a CI step and let it change and commit on its own. maybe...

Unfortunately this completely breaks external RSS feeds with direct torrent links to RuTracker. Can the old rutracker_auth plugin be restored and work in parallel with this?

@n00buk In that case wouldn't it be fine to just disable the url rewriting for the task?

disable:
  - urlrewriting

@BrutuZ, I might be doing it wrong, but it didn't work. Here is what i tried...

task-name:
  rss: {? key.rssurl ?}
  accept_all: yes
  rutracker_auth:
    username: \''{? key.rut_u ?}'\'
    password: \''{? key.rut_p ?}'\'
  set:
    path: '{? folder.ong_dl ?}'
  disable: urlrewriting
  transmission:
    host: localhost
    port: 9091
    ratio: -1
    username: '{? key.tr_u ?}'
    password: '{? key.tr_p ?}'

... and what I got ...

2020-07-08 22:05:47 INFO     transmission  task-name      Trying to connect to transmission...
2020-07-08 22:05:47 INFO     transmission  task-name      Successfully connected to transmission.
2020-07-08 22:05:47 VERBOSE  backlog       task-name      Added 3 entries from backlog
2020-07-08 22:05:47 VERBOSE  details       task-name      Produced 4 entries.
2020-07-08 22:05:47 VERBOSE  task          task-name      ACCEPTED: `torrent name 1` by accept_all plugin
2020-07-08 22:05:47 VERBOSE  task          task-name      ACCEPTED: `torrent name 2` by accept_all plugin
2020-07-08 22:05:47 VERBOSE  task          task-name      ACCEPTED: `torrent name 3` by accept_all plugin
2020-07-08 22:05:47 VERBOSE  task          task-name      ACCEPTED: `torrent name 4` by accept_all plugin
2020-07-08 22:05:47 CRITICAL plugin        task-name      Host unreachable.
2020-07-08 22:05:47 WARNING  task          task-name      Aborting task (plugin: rutracker_auth)