Any plans for audience / critic rating filtering?

[XariZaru]

A lot of my users add a lot of things they want to watch one time and then let it build up in my server. I was hoping to use Jellysweep with some criteria like:

if audience_score < 60% and critic_score < 60% and num_times_watched <= 1 and quality_profile != "Lossless|Best":
     delete item

However, I don't see any filter options for audience score / critic score. Do you have plans for this in the future?

[jon4hz]

I didn't plan to implement something like that and I'm not sure if that logic fits in perfectly with jellysweep.

Especially the num_times_watched isn't something that I'd want to add.

But a filter options like audience_score_threshold and critic_score_threshold is something that could be added very easily.

That would allow you to write a config like:

filter:
  last_stream_threshold: 30
  audience_score_threshold: 60
  critic_score_threshold: 60

This would delete all content that has a rating lower than 60% and wasn't streamed for 30 days.

What do you think about this approach?

[XariZaru]

That sounds perfect to me.

…

On Sun, 4 Jan 2026 at 12:57 pm, Jonah ***@***.***> wrote: I didn't plan to implement something like that and I'm not sure if that logic fits in perfectly with jellysweep. Especially the num_times_watched isn't something that I'd want to add. But a filter options like audience_score_threshold and critic_score_threshold is something that could be added very easily. That would allow you to write a config like: filter: last_stream_threshold: 30 audience_score_threshold: 60 critic_score_threshold: 60 This would delete all content that has a rating lower than 60% and wasn't streamed for 30 days. What do you think about this approach? — Reply to this email directly, view it on GitHub <#234 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEL5FARQVBTVKK2HY532TP34FFIBVAVCNFSM6AAAAACQU6Y5QOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBQGY3TCNQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[XariZaru]

Would something like “number of unique watches” be more akin to your filtering standards? For example, if I have 10 users and only User A watched the movie, that would be 1 watch. Doesn’t matter how many times User A watched the movie.

The purpose of this filter then specifically targeting movies that were added to be watched by just 1 person, or does this fall outside the scope?