Remove yggtorrent support

[HLFH]

Hi,

YggTorrent is no longer supported because of Cloudflare protections.
The current issue should be closed and classified as won't fix.

Before Jackett is able to bypass Cloudflare protections thanks to some new contributors, it is best to remove the yggtorrent files as it is no longer supported.

In the mean time, I recommend everyone to use their own scraper for yggtorrent or - more easily - to migrate to an alternative such as the torrent tracker that has recently been implemented into Jackett: ONLYscene.

[ngosang]

You need to do some changes in the updater code too.
Anyway this issue is affecting more sites, Jackett developers have to make a global decision about Cloudflare.

[HLFH]

Not sure what you mean by the required changes in the updater code.

On a different project, the Cloudflare bypass issue has never been fixed.
wallabag is an alternative to the Pocket read-it-later service: wallabag/wallabag#1399 ; and five years laters, neither the core team nor the contributors fixed it.

Happily, more developers have worked in the last years to tackle this issue, so I guess Jackett will be able to fix it thanks to its community.

[Ekhozie]

I don't think this PR is still required as cloudflare has been removed from yggtorrent (see #8840) and everything is now working well.

[HLFH]

@Ekhozie Yes,

I don't think this PR is still required as cloudflare has been removed from yggtorrent (see #8840) and everything is now working well.

I understand it and it works. I'll close this PR as soon as the discussion is over, that the #8840 issue is closed, and that a global issue concerning the bypass of CloudFlare Security Protections is submitted.

[cadatoiva]

One thing we could do to remain relatively lightweight and still solve the JS challenges relatively easily is to have a node.js component to the system and run that as the challenge solver: https://stackoverflow.com/questions/15136952/can-a-c-sharp-application-communicate-with-node-js-code

Since it's already a JS engine, it should be able to run the code from the site to parse, and then pass along the finished result.

Other option is to look for progress on the javascript interpreter front.

[ngosang]

@Guisch I have been working in a NodeJS server based on this code #8840 (comment) but it's generic, it works with all sites and challenges. And a C# handler/interceptor that is able to send the requests to the NodeJS server and get the cookies. Implements this #8840 (comment)

All is implemented and working but it's no reliable because Cloudflare is able to detect Selenium and Puppeteer and It shows the hCaptcha instead of the JS challenge.

• Stealth plugin is being detected by cloudflare Hcaptcha security page berstend/puppeteer-extra#208
• Anybody noticing increased detection rate recently? berstend/puppeteer-extra#213
• https://github.com/berstend/puppeteer-extra/issues

I can share all the code but I think this is going to be the cat and mouse game again...

[Aditya94A]

I can share all the code but I think this is going to be the cat and mouse game again...

Please do, we gotta start somewhere 😁

[ngosang]

This is the server source code => https://github.com/ngosang/FlareSolverr
I will publish the C# interceptor source code soon.

@Guisch @ All Any help to improve the code or to bypass Cloudflare detection will be appreciated.

[ngosang]

For those interested in the Cloudflare problem that affects other trackers see #9029