Blacklist and or filter by release level

[NotLazy]

Description

When trying to discover new movies, there are often results which have not been released yet.

Desired Behavior

It would be nice to be able to filter by release level (eg. theatrical, digital, etc.), or even to be able to prevent users from being able to see anything which has not met a certain release threshold, especially when requesting via a collection.

Additional Context

This is related to #1346 and #1739 but is not a duplicate because this would allow user-level and admin-level restriction of the actual visibility of unreleased/partially released content.

Code of Conduct

• I agree to follow Seerr's Code of Conduct

[seerr-bot]

Possible duplicate detected (from bulk scan)

This issue may be a duplicate of the following (detected via semantic similarity + LLM review):

• Filter Release Date Tied To Specific Type of Release #579 (70% match) — Filter Release Date Tied To Specific Type of Release

  Both propose filtering by release type, but with different implementation details

• Add General Setting: Blacklist Content with Ratings #1796 (65% match) — Add General Setting: Blacklist Content with Ratings

  Both involve blacklisting content based on specific criteria, but with different attributes

A maintainer will review this. If this is not a duplicate, no action is needed.

[keldian]

The ability to hide/block titles that on TMDb do not have "Physical" nor "Digital" release types at all seems obvious, since it directly means those titles are unobtainable, and the request would be impossible to fulfil. Why is this not implemented yet?

[fallenbagel]

The ability to hide/block titles that on TMDb do not have "Physical" nor "Digital" release types at all seems obvious, since it directly means those titles are unobtainable, and the request would be impossible to fulfil. Why is this not implemented yet?

Not really. Seerr is designed to be future requestable too. Because when you request it goes to arr and gets monitored so you dont habe to worry about waiting for it to release physical or so. And this is how majority of users use seerr. Its like request and forget kinda thing until it becomes available.

[keldian]

Not really. Seerr is designed to be future requestable too. Because when you request it goes to arr and gets monitored so you dont habe to worry about waiting for it to release physical or so. And this is how majority of users use seerr. Its like request and forget kinda thing until it becomes available.

I wasn't referring to unreleased titles. There's a massive catalog of titles that premiered years ago that do not have physical/digital release dates set at all. Also, you're acting like I suggested it should be mandatory or a default. It should absolutely be an option.

Your reply is off the mark and I fully maintain what I said.

[fallenbagel]

Not really. Seerr is designed to be future requestable too. Because when you request it goes to arr and gets monitored so you dont habe to worry about waiting for it to release physical or so. And this is how majority of users use seerr. Its like request and forget kinda thing until it becomes available.

I wasn't referring to unreleased titles. There's a massive catalog of titles that premiered years ago that do not have physical/digital release dates set at all. Also, you're acting like I suggested it should be mandatory or a default. It should absolutely be an option.

Your reply is off the mark and I fully maintain what I said.

I maintain what I said too. Just because they do not have a physical/digital release do not mean they should not be requestable. Your reply came off as it should be the default so I replied to that. Its quite obvious why its not an option to block/hide isn't it? Because nobody implemented it. We are all volunteers who work in our free time. Plus blocklist is a feature that was very recently introduced too. Seerr is a fully open source project that relies on external contributions and us sacrificing time from our personal lives so we don't really owe it to anybody. So we implement what we can when we can. And this issue is still opened and not closed as not planned. Which means it's something we consider to be added. Feel free to open a PR.