He included an unlicensed H.264 decoder in his app. He could have avoided this by either using Chrome's built-in APIs[1], utilizing Cisco's free H.264 implementation[2], or simply paying the license fees himself. Google and Cisco are already paying the fees to make developers lives easier.
As much as I hate patent trolls, this isn't really patent trolling.
To make matters worse, I informed Koushik Dutta about this possible issue back in 2015[3] and he closed my GitHub issue and ignored it. I'm not surprised at the outcome.
As much as I hate patent trolls, this isn't really patent trolling.
To make matters worse, I informed Koushik Dutta about this possible issue back in 2015[3] and he closed my GitHub issue and ignored it. I'm not surprised at the outcome.
[1]: https://developer.chrome.com/native-client/pepper_dev/c/stru...
[2]: http://www.openh264.org/
[3]: https://github.com/koush/vysor.io/issues/84