How far is D* supposed to go to protect a user from him or herself? Some solutions can't ever be 100% perfect.
Then it shouldn't be called "Keep until I Delete", IMO, because that implies you have control over deletion, not the HR20. Customer service issue.
Agree. Good idea, IMO
More user confusion. Works one way with the BLUE button, another with the KUID setting. Hence the origin of the WL suggestion to just make it work just like TiVo. It's a proven method that's been working for the TiVo crowd for a few years. The one thing it doesn't cover can be covered by your Limit Exceeded idea, IMO.
Just my .02. Others, please chime in. /s
IMHO: As proven by TiVo, is the problem there.
TiVo's way violates one of it's own statements.
Because IMHO: It doesn't work in TiVo's implementation (as see my example with 24 and other shows).
I "TOLD" the unit in the Series Pass/Link, to record new episodes.
So if it stopped recording at 5, then it didn't do what I told it to do with that statement....
So the debate is... which statement has the priority over the other:
Keep it Until "I" Delete it.... or Record the New Episode... which one?
KUID should be totally re-worded so it is clear, that it ONLY relates to automatic deletion due to hard drive space... (and the functionality completely in all cases applies to that fact).
It should be severed from any calculations that KAM uses, and should be independent... and should thus only be looked at by the automatic deletion logic (and excluded) when the functionality is run to clear space for future recordings.
And you are correct, that you can go only so far to protect users... but right now you have cases, that can not be settled by the current options.
You have to go 5 or ALL... but just because 10 is a larger number, what about 15, 30, ect... (I have seen those requests in TiVo land, and here)..