(Replying to PARENT post)
Obviously, safeguards for personal things is important, but the other way you see passwords used (at least in fiction) is for groups - secret door knock, "What's the password?" said by some bouncer through an eye slit in a door [1]. In this perspective, password sharing is a norm. It can be seen as a means to signifying your membership in a group... that shares Netflix.
(Replying to PARENT post)
There were dozens of times in the 2 months that I had the service that I was unable to stream, because I had hit a "concurrent streams" limit.
Switching between devices, having my browser auto-login (which would take up a "slot"), And the fun bug they had for a while where if I started a stream on my phone, then "cast" it to a chromecast, it would count as 2 streams, and due to a limitation where playstations were given their own dedicated "slots" meant that 2 people couldn't watch on a chromecast at any given time even though I should have had 5 simultaneous streams allowed.
I ended up canceling the service because of it, and I appreciate the limits that Netflix has much more.
(Replying to PARENT post)
(Replying to PARENT post)
The HBO 3rd party app streams + the xfinity app streams + the ESPN app streams + the USA Network app streams [ + 30 other channel-specific apps ] all have to report to a single central place for each cable provider, if you're going to do this effectively, right?
(Replying to PARENT post)
What is it with engineers willing to brainwash themselves regarding what constitutes a โgood compromiseโ within the context of what their paycheck depends on?
(Replying to PARENT post)
Implmenting stream limits is tricky, as there are edge cases that are hard to get right. However, common DRM services like Widevine and Playready have adopted the extensions necessary to implement stream limits, so there are already "of-the-shelf" solutions.
In short, this is a non-issue with available technical solutions.
Full disclosure: I'm an engineer at Netflix who works on cable set-top boxes.