5 ms·

Is Disney+ expected to work fully before launch date? Isn't in 'testing' right now as described by the author? Why is everything expected to be perfect while st

Is Disney+ expected to work fully before launch date? Isn't in 'testing' right now as described by the author? Why is everything expected to be perfect while still in testing? From this text, it sounds like Disney is actively working on the issue. The product has not launched yet. I'm not sure what the problem is. Aside from a faster initial customer support response (for a product that isn't even out!) would could Disney have done differently here? I understand that Disney+ may not launch with (or ever have) Linux support, and that would suck. But no evidence of that is presented here. And the author expects a resolution for a complex issue for a pre-launch product in testing phase from a major corporation within days? That seems aggressive and unrealistic timeline to expect a fix. Edit: The author writes "Their so called help-center does not even know about "Error Code 83"" (with some attitude and prejudice, I'll note); but also writes that Disney responded with "We are familiar with Error 83.". Confusing.

jchw 7y ago
The thing is, as they cover in their post, there’s nothing to “fix.” It isn’t broken. The error is actually that it refuses to run without a higher security level than many platforms support.
- Mindwipe 7y ago
  It runs in Chrome on Windows, which also only supports Widevine Level 3, same as Linux. The post is just... not very good and full of factual errors.
  - jchw 7y ago
    This may very well be true, I’d like to note I don’t claim to know anything about how Widevine works. Of course, this is a very different criticism of the post.
newnewpdro 7y ago
You're ignoring the analysis that Disney+ seems to be blocking use entirely at the lower "security level" assessed by Widevine. It would not take significant time or effort for them to change the threshold value if it were something they considered broken. It seems prudent at this point to avoid becoming a paying customer until they address it, if you care about this sort of thing.
- cryptoz 7y ago
  > It would not take significant time or effort for them to change the threshold value if it were something they considered broken. Do you have reason to believe this? To me that sounds like a complicated change with significant potential business impacts. Have they signed contracts already where this kind of security is ambiguous? Does changing the flag actually solve the issues on all devices or do other issues present, since they have been untested? Testing must happen post-change, I would imagine. The issue still sounds complex to me. I use Linux and I want Disney+ to support it, obviously. But I don't see Disney as being in the wrong here (yet) - they're potentially just working on the issue before release. We'll see, I guess.
- Mindwipe 7y ago
  > You're ignoring the analysis that Disney+ seems to be blocking use entirely at the lower "security level" assessed by Widevine. That's because it's wrong. Chrome on Windows only supports Level 3 too, and it works there. (The article incorrectly assumes Level 1 is lower than Level 3. Level 1 is the highest security level, not the lowest.)

jchw 7y ago

The thing is, as they cover in their post, there’s nothing to “fix.” It isn’t broken. The error is actually that it refuses to run without a higher security level than many platforms support.

Mindwipe 7y ago
It runs in Chrome on Windows, which also only supports Widevine Level 3, same as Linux. The post is just... not very good and full of factual errors.
- jchw 7y ago
  This may very well be true, I’d like to note I don’t claim to know anything about how Widevine works. Of course, this is a very different criticism of the post.

newnewpdro 7y ago

You're ignoring the analysis that Disney+ seems to be blocking use entirely at the lower "security level" assessed by Widevine. It would not take significant time or effort for them to change the threshold value if it were something they considered broken. It seems prudent at this point to avoid becoming a paying customer until they address it, if you care about this sort of thing.

cryptoz 7y ago
> It would not take significant time or effort for them to change the threshold value if it were something they considered broken. Do you have reason to believe this? To me that sounds like a complicated change with significant potential business impacts. Have they signed contracts already where this kind of security is ambiguous? Does changing the flag actually solve the issues on all devices or do other issues present, since they have been untested? Testing must happen post-change, I would imagine. The issue still sounds complex to me. I use Linux and I want Disney+ to support it, obviously. But I don't see Disney as being in the wrong here (yet) - they're potentially just working on the issue before release. We'll see, I guess.
Mindwipe 7y ago
> You're ignoring the analysis that Disney+ seems to be blocking use entirely at the lower "security level" assessed by Widevine. That's because it's wrong. Chrome on Windows only supports Level 3 too, and it works there. (The article incorrectly assumes Level 1 is lower than Level 3. Level 1 is the highest security level, not the lowest.)