veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

295
active users

#codecs

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://wetdry.world/@ezra" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ezra</span></a></span> personally I think <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a> should be forced.to implement <a href="https://infosec.space/tags/AV1" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AV1</span></a> &amp; <a href="https://infosec.space/tags/WebM" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">@<span>EUCommission</span></a></span> could mandate <a href="https://infosec.space/tags/OpenStandards" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#<span>patents</span></a> and espechally <a href="https://infosec.space/tags/SoftwarePantents" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwarePantents</span></a>, we'd have way better <a href="https://infosec.space/tags/Codecs" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#<span>FLOSS</span></a> <a href="https://infosec.space/tags/Codec" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#<span>H265</span></a> wasn't <a href="https://infosec.space/tags/patented" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>patented</span></a> and facing <a href="https://infosec.space/tags/PatentTrolls" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PatentTrolls</span></a> and <a href="https://infosec.space/tags/rentseekers" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#<span>CCSS</span></a> &amp; <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#<span>MPEGLA</span></a>-Member) is <a href="https://wetdry.world/@ezra/114407901007915827" rel="nofollow noopener" target="_blank">at the root of the problem</a>!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://hessen.social/@ustralien" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ustralien</span></a></span> and even then:</p><p>Modern <a href="https://infosec.space/tags/Codecs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Codecs</span></a> like <a href="https://infosec.space/tags/Speex" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Speex</span></a> and espechally <a href="https://infosec.space/tags/Opus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Opus</span></a> really work great on <a href="https://infosec.space/tags/Mumble" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mumble</span></a> and other solutions like <a href="https://infosec.space/tags/WebCall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebCall</span></a> and <a href="https://infosec.space/tags/SIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SIP</span></a>-Clients like <a href="https://infosec.space/tags/Linphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linphone</span></a>.</p><ul><li>Unless you're stuck on <a href="https://infosec.space/tags/Iridium" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Iridium</span></a>, then <a href="https://infosec.space/tags/Codec2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Codec2</span></a> is the only thing narrowband-efficient enough to work at all...</li></ul>
jbz<p>🎬 AV1 is supposed to make streaming better, so why isn’t everyone using it? <br>—<span class="h-card" translate="no"><a href="https://mastodon.social/@verge" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>verge</span></a></span></p><p>「 Netflix, Microsoft, Google, Amazon, and Meta banded together to develop video compression’s latest evolution: AV1. The companies say the video codec is around 30 percent more efficient compared to other standards like HEVC and the Google-developed VP9, allowing it to deliver higher-quality video at a lower bandwidth 」</p><p><a href="https://www.theverge.com/tech/635020/av1-streaming-netflix-youtube-google-adoption" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">theverge.com/tech/635020/av1-s</span><span class="invisible">treaming-netflix-youtube-google-adoption</span></a></p><p><a href="https://indieweb.social/tags/av1" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>av1</span></a> <a href="https://indieweb.social/tags/codecs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>codecs</span></a> <a href="https://indieweb.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a></p>
jbz<p>🎧 You Didn't Notice MP3 Is Now Free </p><p>「 The MP3 format, once the gold standard for digital audio files, is now free. The licensing and patents on MP3 encoders have expired, meaning you can now include them in your applications without paying royalties. For software developers and audio enthusiasts, this might seem like a big deal 」</p><p><a href="https://idiallo.com/blog/listen-mp3-is-free" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">idiallo.com/blog/listen-mp3-is</span><span class="invisible">-free</span></a></p><p><a href="https://indieweb.social/tags/mp3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mp3</span></a> <a href="https://indieweb.social/tags/patents" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>patents</span></a> <a href="https://indieweb.social/tags/codecs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>codecs</span></a></p>
Kevin Karhan :verified:<p>[<a href="https://infosec.space/tags/TLDR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TLDR</span></a>: JUST TELL ME <em>IF</em> YOUR TABLET CAN DO <a href="https://infosec.space/tags/CALLS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CALLS</span></a>!]</p><p><a href="https://infosec.space/tags/DearVendors" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DearVendors</span></a> of <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Android</span></a>-<a href="https://infosec.space/tags/Tablets" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tablets</span></a>:</p><p>Off all the <a href="https://infosec.space/tags/Functions" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Functions</span></a> you can put into a <a href="https://infosec.space/tags/Specifications" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Specifications</span></a> Sheet of your Devices there's one you should <em>ALWAYS answer clearly</em> on your <a href="https://infosec.space/tags/Website" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Website</span></a>:</p><p><em>DOES YOUR TABLET [with <a href="https://infosec.space/tags/4G" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>4G</span></a> / <a href="https://infosec.space/tags/5G" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>5G</span></a> / …) SUPPORT MAKING PHONE CALLS?</em></p><ul><li><p><em>NOT</em> "It can run <a href="https://infosec.space/tags/WhatsApp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WhatsApp</span></a>" (or <em>whatever shitty <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a> for <a href="https://infosec.space/tags/VoIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VoIP</span></a></em> you think of)...</p></li><li><p><em>NOT</em> "It can do <a href="https://infosec.space/tags/CSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSD</span></a> / <a href="https://infosec.space/tags/HSCSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HSCSD</span></a> / <a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>2G</span></a> / <a href="https://infosec.space/tags/3G" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>3G</span></a> /..."</p></li><li><p><em>But</em> DOES IT SUPPORT <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GSM</span></a>-<a href="https://infosec.space/tags/Calls" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Calls</span></a> (and/or <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VoLTE</span></a>)??</p></li></ul><p>Like: <em>IS IT TOO MUCH TO ASK TO HAVE THAT INFO IN THE SPECSHEETS?</em></p><p>You're obviously able to list all the <a href="https://infosec.space/tags/Codecs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Codecs</span></a> natively supported and the user-available storage as well as supported Frequency Bands, WWAN modes, WiFi channel width and the Display Glass vs. Panel dimensions including DPI of the latter and whether or not it has a hall effect sensor to detect your overpriced 1st party tablet covers!</p><p>Now some folks may ask: <em>"WHY does this matter?"</em> or outright dismiss this as a problem.</p><p>Listen: <br>Not everyone is able or willing to carry <em>two</em> devices when 1 <em>SHOULD BE ENOUGH</em> and also some places (i.e. <a href="https://infosec.space/tags/Turkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Turkey</span></a>) have <a href="https://infosec.space/tags/ImportRestrictions" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ImportRestrictions</span></a> re: <a href="https://infosec.space/tags/MobileDevices" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MobileDevices</span></a>, so having more than 1 <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IMEI</span></a> is already a <em>"NOPE!"</em> by the authorities.</p><ul><li>Also this isn't something one can <em>"fix"</em> post-purchase like installing <a href="https://infosec.space/tags/VLC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VLC</span></a> to decode some obscure file format in Software: Either <em>the <a href="https://infosec.space/tags/Baseband" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Baseband</span></a> and <a href="https://infosec.space/tags/ROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ROM</span></a> support <a href="https://infosec.space/tags/PhoneCalls" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PhoneCalls</span></a> or they don't!</em></li></ul><p>So why do <em>NONE</em> of the <a href="https://infosec.space/tags/Tablet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tablet</span></a> manufacturers allow to <a href="https://infosec.space/tags/search" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>search</span></a> or <a href="https://infosec.space/tags/filter" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filter</span></a> for that???</p><ul><li>Bonus points if you have lazy fucks like <a href="https://infosec.space/tags/HMD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HMD</span></a> (aka. <a href="https://infosec.space/tags/Nokia" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Nokia</span></a>) who literally copy the <a href="https://infosec.space/tags/Safety" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Safety</span></a> &amp; <a href="https://infosec.space/tags/Useage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Useage</span></a> information for all <a href="https://infosec.space/tags/Smartphones" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Smartphones</span></a> and <a href="https://infosec.space/tags/Tablets" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tablets</span></a> and don't even bother to change <em>"Mobile Phone"</em> for <em>"Tablet"</em>.</li></ul><p><em>NO</em>, instead one has to download an <em>obscenely huge <a href="https://infosec.space/tags/PDF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PDF</span></a></em> just to then <a href="https://downloadcenter.samsung.com/content/UM/202410/20241010132004137/SM-X11X_X21X_UM_Open_UU_Ger_Rev.1.2_240925.pdf" rel="nofollow noopener" target="_blank">read on page 34</a> that for any <em>"<a href="https://infosec.space/tags/telephony" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>telephony</span></a>"</em> function you <em>NEED YET ANOTHER DEVICE FROM THE SAME MANUFACTURER AND HAVE TO SIGNUP WITH AN ACCOUNT</em> and even that level of <a href="https://infosec.space/tags/abuse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>abuse</span></a> WON'T GUARANTEE THAT IT WORKS...</p><ul><li>I mean, come on, this <em>ain't</em> some <em>obscure functionality</em> like <a href="https://infosec.space/tags/OMAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OMAPI</span></a> to do some <em>"evil sourcery"</em> like <em>managing an <a href="https://infosec.space/tags/eSIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eSIM</span></a> that is in a <a href="https://infosec.space/tags/SIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SIM</span></a>-Card form factor</em>!</li></ul><p>Pretty shure <em>A LOT</em> of other folks have the same question and ain't willing to get <em>yet another device &amp; <a href="https://infosec.space/tags/SIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SIM</span></a></em> just to recieve <em>the occasional call</em> because <a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechIlliterates</span></a> can't be assed to send an <a href="https://infosec.space/tags/eMail" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eMail</span></a> or learn <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XMPP</span></a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OMEMO</span></a> to message one...</p><ul><li>Obviously they same manufacturers are <em>able and willing</em> to specify <em>f-stops</em> of the built-in cameras and list <em>EVERY SINGLE <a href="https://infosec.space/tags/WEARABLE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WEARABLE</span></a></em> they made and certify as <em>'compatible'</em> with, as if <em>anyone</em> is gonna take their non-<a href="https://infosec.space/tags/waterproof" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>waterproof</span></a> <a href="https://infosec.space/tags/Tablet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tablet</span></a> for a marathon or god forbid triathlon...</li></ul><p><a href="https://infosec.space/tags/Rant" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Rant</span></a> <a href="https://infosec.space/tags/TechSupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechSupport</span></a> <a href="https://infosec.space/tags/Technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Technology</span></a> <a href="https://infosec.space/tags/Support" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Support</span></a> <a href="https://infosec.space/tags/Sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sysadmin</span></a> <a href="https://infosec.space/tags/Procurement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Procurement</span></a> <a href="https://infosec.space/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IT</span></a> <a href="https://infosec.space/tags/SpecSheet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SpecSheet</span></a> <a href="https://infosec.space/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tech</span></a></p>
Jeff Fortin T. (風の庭園のNekohayo)<p>Honored to have been promoted to the prestigious rank of Lead&nbsp;GNOME&nbsp;Dev™, thanks to the warm endorsement received in <a href="https://octodon.social/@dgold/112621388637875424" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">octodon.social/@dgold/11262138</span><span class="invisible">8637875424</span></a></p><p>Finally, my decades of <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> contributions are being recognized in equal measure to my role as CEO or senior partner of various businesses &amp; non-profits ☺️</p><p>I must clarify, however, that I never stated my personal workflow as the limiting factor in changing to more modern <a href="https://mastodon.social/tags/codecs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>codecs</span></a> for <a href="https://mastodon.social/tags/GNOMEShell" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNOMEShell</span></a>'s video recorder: <a href="https://mastodon.social/@nekohayo/112615076552383375" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mastodon.social/@nekohayo/1126</span><span class="invisible">15076552383375</span></a></p><p><a href="https://mastodon.social/tags/GNOME" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNOME</span></a> <a href="https://mastodon.social/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a></p>
voya :linux: :mastodon:<p>Finally I get it done!</p><p>You may wish to know how to enable <a href="https://social.vivaldi.net/tags/ffmpeg" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ffmpeg</span></a> <a href="https://social.vivaldi.net/tags/codecs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>codecs</span></a> support for <a href="https://social.vivaldi.net/tags/Vivaldi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Vivaldi</span></a> / other <a href="https://social.vivaldi.net/tags/Chromium" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chromium</span></a> browsers on <a href="https://social.vivaldi.net/tags/aarch64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>aarch64</span></a> <a href="https://social.vivaldi.net/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> systems:</p><p><a href="https://medium.com/@voyagercy/enable-ffmepg-codecs-support-for-vivaldi-on-aarch64-linux-d6b5f29d753a" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">medium.com/@voyagercy/enable-f</span><span class="invisible">fmepg-codecs-support-for-vivaldi-on-aarch64-linux-d6b5f29d753a</span></a></p>