alt Hacker NewsHow is the *arr stack so fracking complicated? Once upon a time, all you needed was a browser, a torrent client, and VLC. Maybe your torrent client had an RSS feed built in.
Now you need 9 different pieces of software that end in *arr, all of which implement parts of the solution that you want and parts that you don't, and none of them is even a torrent client!
And they don't even work with torrent sites reliably, so people then spend money on a Usenet subscription like it's 1990 again.
Replies
It works great. Family loves being able to self serve media requests.
Blame copyright laws.
Any all-in-one solution is going to be considered illegal at face value if it is obviously designed to circumvent copyright.
But if you split all the pieces of the solution up into separate pieces of software that can't do much illegal by themselves, you can always claim plausible deniability as the maintainer.
After all, you aren't going to be downloading torrents with Sonarr, you aren't going to be looking up information about shows with Jackett, and you aren't going to be automating your downloads with qBittorrent. If you link them all together with APIs, though, they do everything automatically.
As for the issue demonstrated here, it's just a long-standing problem in Sonarr and Radarr that even when it detects that a torrent is bad, it just sits there holding onto a virus until you override it with a working torrent, instead of just dumping the bad data and trying again.
You can still manually download a torrent, open it in your client, and then open the file in VLC.
You can also automate 99% of it with the *arr stack and completely forget about it.
What is the issue? There is more choice now?