irelephant [he/him]@lemmy.dbzer0.comM to iiiiiiitttttttttttt@programming.devEnglish · 12 days agoCompression!lemmy.dbzer0.comimagemessage-square30fedilinkarrow-up1432arrow-down17
arrow-up1425arrow-down1imageCompression!lemmy.dbzer0.comirelephant [he/him]@lemmy.dbzer0.comM to iiiiiiitttttttttttt@programming.devEnglish · 12 days agomessage-square30fedilink
minus-squarexoggy@programming.devlinkfedilinkEnglisharrow-up75arrow-down1·12 days agoTurns out we’re already doing a lot of compression at the file and filesystem level.
minus-squareOpisek@piefed.blahaj.zonelinkfedilinkEnglisharrow-up32·12 days agoNot necessarily. For example, you can’t really compress encrypted files. You can certainly try but the result will likely be what the meme portrays.
minus-squareRandelung@lemmy.worldlinkfedilinkarrow-up31·12 days agoTurns out pseudo random byte streams don’t really repeat that often.
minus-squareSkyeStarfall@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up5·11 days agoWe just need to develop an algorithm to compress random byte streams, easy
minus-squareWolfLink@sh.itjust.workslinkfedilinkEnglisharrow-up6·12 days agoMedia files are always thoroughly compressed (except in certain settings like professional video and audio work).
minus-squarerainwall@piefed.sociallinkfedilinkEnglisharrow-up5·12 days agoMedia files can can benefit from a codec change. Going from h264 to h265/hevc can net a 30-50% reduction in size for almost no quality loss. The only trade off is increased cpu usage if the client doesnt have hardware h265 support and the time to do the transcoding.
minus-squareulterno@programming.devlinkfedilinkEnglisharrow-up3·11 days agoAnd then comes AV1, with crazily varying quality/compression for different source materials.
minus-squareOpisek@piefed.blahaj.zonelinkfedilinkEnglisharrow-up1·11 days agoI don’t see how that relates to encryption.
minus-squareWolfLink@sh.itjust.workslinkfedilinkEnglisharrow-up2·11 days agoIt’s more relevant to the previous comment as an example of how we are doing a lot of compression at the filesystem level. The files that are typically largest are already quite thoroughly compressed.
Turns out we’re already doing a lot of compression at the file and filesystem level.
Not necessarily. For example, you can’t really compress encrypted files. You can certainly try but the result will likely be what the meme portrays.
Turns out pseudo random byte streams don’t really repeat that often.
We just need to develop an algorithm to compress random byte streams, easy
Media files are always thoroughly compressed (except in certain settings like professional video and audio work).
Media files can can benefit from a codec change. Going from h264 to h265/hevc can net a 30-50% reduction in size for almost no quality loss.
The only trade off is increased cpu usage if the client doesnt have hardware h265 support and the time to do the transcoding.
And then comes AV1, with crazily varying quality/compression for different source materials.
I don’t see how that relates to encryption.
It’s more relevant to the previous comment as an example of how we are doing a lot of compression at the filesystem level.
The files that are typically largest are already quite thoroughly compressed.