He included an unlicensed H.264 decoder in his app. He could have avoided this by either using Chrome&#x27;s built-in APIs[1], utilizing Cisco&#x27;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.<p>As much as I hate patent trolls, this isn&#x27;t really patent trolling.<p>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&#x27;m not surprised at the outcome.<p>[1]: <a href="https:&#x2F;&#x2F;developer.chrome.com&#x2F;native-client&#x2F;pepper_dev&#x2F;c&#x2F;struct_p_p_b___video_encoder__0__2" rel="nofollow">https:&#x2F;&#x2F;developer.chrome.com&#x2F;native-client&#x2F;pepper_dev&#x2F;c&#x2F;stru...</a><p>[2]: <a href="http:&#x2F;&#x2F;www.openh264.org&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.openh264.org&#x2F;</a><p>[3]: <a href="https:&#x2F;&#x2F;github.com&#x2F;koush&#x2F;vysor.io&#x2F;issues&#x2F;84" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;koush&#x2F;vysor.io&#x2F;issues&#x2F;84</a>