• 0 Posts
  • 6 Comments
Joined 5 months ago
cake
Cake day: February 8th, 2025

help-circle

  • That’s a terrible way to put it and sincerely misguided in my opinion. I have a handful of public indexers, they work fine in 99.99% of the cases for my needs. In fact, never before I’ve had this issue until recently, with two unreleased episodes that were fake files. For me, not allowing the unreleased episodes is just another layer of security. In other words, using your example, I don’t want the water filter for my car to use the bad gas station, I want to get the water filter to make sure that if there’s ever some water by accident or not then it won’t get to the engine… If I see the indexers or trackers start publishing a lot of fake stuff it will get removed, but from public indexers I understand if there’s something ever getting past, and I don’t want the devs of some software deciding that me requiring that a show has been aired before I even try to download it is dumb.


  • Precisely, just make it optional, hell even just apply the way it is now as default, but give the option to those that prefer it. But each time it is requested it gets shot down immediately and when people ask why not make it optional no one answers.

    The needed change is not even that complex and someone provided the link to the pull request for radarr that implemented the similar function (actually even more complex as it has more options for movies). I’ve even considered trying to do it myself, but its quite the effort to prepare the dev environment, make the change, test it and make the pull request just to get the same dev shoot it down just out of spite. If the feature request was still open even if the usual devs don’t want to do it then it would show that they would accept it…



  • I went down the rabbit hole on this the other day as I was trying to find a way to block unreleased episodes. It’s unbelievable to me the resistance they put against such a simple feature. Like no one is requesting to force it that way, just give the option to make it so.

    The two reasons I saw for canceling the feature request over menu duplicates is the “use better trackers” mainly but also that shows are so often released or leak early they this setting would block you from getting them faster… Those are the dumbest reasons ever to not provide a setting that people are literally asking over and over again for.

    The change is done for radarr so it might not be terribly hard to adapt into sonarr. Being open source I would have expected someone to do the change already but if they fight against it so much as a principle who would expect them to approve the change…


  • yyprum@lemmy.dbzer0.comtoFuck AI@lemmy.worldThe Perfect Response
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    3 months ago

    I guess it is inevitable that self centred ego-stroking bubble communities appear in platforms such as Lemmy. Where reasoned polite discussion is discouraged and opposing opinions are drowned.

    Well, I’ll just leave this comment here in the hope someone reads it and realises how bad these communities actually are. There’s a lot to hate about AI (specially companies dedicated to sell it), but not all is bad. As any technology, is about how you use it and this kind of community is all about cancelling everything and never advance and improve.