Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://wetdry.world/@ezra" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ezra</span></a></span> personally I think <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Apple</span></a> should be forced.to implement <a href="https://infosec.space/tags/AV1" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AV1</span></a> & <a href="https://infosec.space/tags/WebM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebM</span></a> and that <span class="h-card" translate="no"><a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>EUCommission</span></a></span> could mandate <a href="https://infosec.space/tags/OpenStandards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandards</span></a>. </p><ul><li>As for quality, were it not for <a href="https://infosec.space/tags/patents" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>patents</span></a> and espechally <a href="https://infosec.space/tags/SoftwarePantents" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SoftwarePantents</span></a>, we'd have way better <a href="https://infosec.space/tags/Codecs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Codecs</span></a>, but this way people engineering a <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FLOSS</span></a> <a href="https://infosec.space/tags/Codec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Codec</span></a> are constantly required to specifically <em>avoid</em> infringement of Patents and other IP by <em>not using anything remotely related to it</em>...</li></ul><p>Also if <a href="https://infosec.space/tags/H265" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>H265</span></a> wasn't <a href="https://infosec.space/tags/patented" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>patented</span></a> and facing <a href="https://infosec.space/tags/PatentTrolls" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PatentTrolls</span></a> and <a href="https://infosec.space/tags/rentseekers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rentseekers</span></a> we'd see way better quality there as well.</p><ul><li>Cuz <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CCSS</span></a> & <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FLOSS</span></a> can't share code nor expertise at all.</li></ul><p>And yes, Apple (<a href="https://infosec.space/tags/MPEGLA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MPEGLA</span></a>-Member) is <a href="https://wetdry.world/@ezra/114407901007915827" rel="nofollow noopener noreferrer" target="_blank">at the root of the problem</a>!</p>