Server-Side Passout Protection

Feature Suggestions
, ,
1

As a server owner, if someone actually wants to spend a 12-hour day rotting on the couch and watching media from my libraries, I’m fine with that. That said, I think we should have the option to discourage/disable the “it’s on for background noise and I fell asleep” or “I left the house and forgot to turn it off” occurrences. Something similar to Netflix’s “Are you still watching?” feature, configurable/enforceable on the server-side that can’t be overridden by client-side settings.

e.g. If I have my server set to “require user confirmation every 3 hours” and a user has their passout protection set to “never prompt,” they should still be prompted 3 hours into their streaming session if they’re pulling from my libraries. Again, I don’t mind if they actually want to have a media binge day, and clicking “yep, still here!” every few hours is a reasonable ask in exchange for limiting my wasted bandwidth, power bill increases, and hardware wear and tear.

4 Likes
2

Next level support would be some way to set compound thresholds, possibly factoring in the library type. i.e.:

We don’t want to interrupt someone just because they’re watching LOTR:ROTK (3h21m) and our threshold is set at 3 hours.

We don’t want to interrupt someone less than an hour into their viewing experience just because they’re watching Adventure Time (~12 min episodes) and we have our threshold set at 4 episodes.

3

Yeah I agree with you, and if they add it it would be nice is it was configurable by number of hours or number of plays before interaction is required. I have a few friends that need noise to sleep and like to fall asleep to shows, then often forget about it in the morning because their tv auto turns off ant it plays while they are at work. I was really surprised that passout feature wasnt server side considering everything plex adds you think something so simple would also be server side.