TechHub

1 post1 participant0 posts today

Kevin Karhan :verified:<a href="https://hai.z0ne.social/@Erpel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Erpel</a> that's how I felt when I first read about <a href="https://en.wikipedia.org/wiki/Secure_Communications_Interoperability_Protocol" rel="nofollow noopener noreferrer" target="_blank">SCIP</a>, the successor to <a href="https://en.wikipedia.org/wiki/STU-III" rel="nofollow noopener noreferrer" target="_blank">STU-III</a> and uses <a href="https://en.wikipedia.org/wiki/Mixed-excitation_linear_prediction" rel="nofollow noopener noreferrer" target="_blank">MELPe</a>, an even more proprietary version of <a href="https://infosec.space/tags/MELP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MELP</a>, as <a href="https://infosec.space/tags/Vocoder" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Vocoder</a>!

Kevin Karhan :verified:<a href="https://mastodon.online/@pawagner" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@pawagner</a> in this case the person was (presumably amidst the background noise) in a callcenter and refused to acknowledge it's their fault and responsibility to not have noise AND legible audio quality.<a href="https://infosec.space/tags/Iridium" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Iridium</a> (<a href="https://infosec.space/tags/AMBE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AMBE</a>) <a href="https://infosec.space/tags/NATO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NATO</a>-Radio (<a href="https://infosec.space/tags/MELP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MELP</a> & <a href="https://infosec.space/tags/MELPe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MELPe</a>) and even <a href="https://infosec.space/tags/Codec2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Codec2</a> is more legible than they were...

OS/1337<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a> The sad part is that you are in fact correct.The only thing <a href="https://infosec.space/tags/Copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Copyleft</a> like <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a>, <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> and espechally <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssholeLicensing</a> of the <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a>, <a href="https://infosec.space/tags/RHEL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RHEL</a> and <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#grsecurity</a> kind can do is commit <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssetDenial</a> and even that is flaky as one can only put actual <a href="https://infosec.space/tags/code" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#code</a> under a license and not an implementation of something like a <a href="https://infosec.space/tags/Codec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Codec</a>......But those are usually covered by <a href="https://infosec.space/tags/patents" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#patents</a> and other legalese trolling efforts, like the way <a href="https://infosec.space/tags/MELP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MELP</a> / <a href="https://infosec.space/tags/MELPe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MELPe</a> is licensed so everyone who doesn't want to exclusively make a radio for NATO / U.S. DoD has to arrange a licensing deal woth half a dozen tech giants, so <a href="https://infosec.space/tags/Codec2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Codec2</a> had to be made... <a href="https://en.wikipedia.org/wiki/Mixed-excitation_linear_prediction" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://en.wikipedia.org/wiki/Mixed-excitation_linear_prediction</a> <a href="https://en.wikipedia.org/wiki/Codec_2" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://en.wikipedia.org/wiki/Codec_2</a>As of now I am considering to relicense my content under <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#0BSD</a> and sinve very few of my projects have any external contributions, this should be trivial to do so.

Recent searches

Search options

Administered by:

Server stats:

#melp