Post by @Federation_Bot

New #blog #post: Gratitude Day 11: Lossy Compression Algorithms

https://rldane.space/gratitude-day-11-lossy-compression-algorithms.html

110 words

cc: my wonderful #chorus: @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @stfn @golemwire

(I will happily add/remove you from the chorus upon request! :)

#rlDaneWriting #blost #SeptemberTheme #SeptemberBloggingTheme #SepThemeBear #SeptemberGratitude #gratitude #thankfulness #algorithms #compression #compSci #algorithmic #Graphics #MPEG #JPEG #DCT #Video

Gratitude Day 11: Lossy Compression Algorithms

#dct #mpeg #septembergratitude #septemberbloggingtheme #thankfulness #septhemebear #septembertheme #jpeg #compression #rldanewriting #chorus #algorithmic #compsci #blost #graphics #video #gratitude #blog #algorithms #post

1 Boost

0 Likes

Tim Chase

@gumnos@mastodon.bsd.cafe last wk.

@rl_dane

I like to joke that, if you're willing to accept lossy compression, rm(1) gives you the best. Nothing else can touch its 100% compression ratio 😆

R.L. Dane :Debian: :OpenBSD: :FreeBSD: 🍵 :MiraLovesYou:

@rl_dane@polymaths.social last wk.

@gumnos

Aye, the slightly more convoluted version I've heard is something akin to lossy run-length encoding...

"Since all data is 1s and 0s, and since a zero is just... zero, let's remove all of the useless zeros in your data, and all you're left with is a long string of ones. Then, let's encode the run length of the 1s as a binary number. Then, you can re-apply the same algorithm to continually shorten the data by a great factor, eventually arriving at just a single binary 1.
Implementing the decompression algorithm is an exercise left to the reader. ;)"

BT Free Social