Except that's just a fantasy scenario and not how Netflix actually works or would work on FreeBSD.
The problem is there is no port of Silverlight with the necessary DRM. The latter is unethical in the context of free software.
However, from what I've read, Netflix intend on switching fully to HTML5 in the near future. This will make their platform OS-agnostic, while still benefiting from things like Encrypted Media Extensions (EME).
How is an open source browser like Firefox supposed to implement Encrypted Media Extensions without leaking the keys to anyone who decides to grab the source code?
In the same way Firefox implements Silverlight today: It's still a binary plugin that talks to the OS for some "secure path", but it's only the decryption in the closed path, instead of the entire playback experience. I don't think HTML5/EME will get Linux/BSD et al users watching Netflix any more than they were before.
Though breaking EME is probably more interesting for a certain class of developer than implementing all of Silverlight with DRM is.
The problem is there is no port of Silverlight with the necessary DRM. The latter is unethical in the context of free software.
However, from what I've read, Netflix intend on switching fully to HTML5 in the near future. This will make their platform OS-agnostic, while still benefiting from things like Encrypted Media Extensions (EME).