People are passing this off as silly, but there's a valid concern here - whether the lossless compression algorithms can actually infect the source material bas

People are passing this off as silly, but there's a valid concern here - whether the lossless compression algorithms can actually infect the source material based off of how it interacts with the hardware. I've noticed this myself while coding - late at night, my software works great when it is all uncompressed and spread out in my IDE, but after I commit it (undoubtedly to remote hard drives that compress my code), it's pulled by others, and sometimes those other people experience bugs. The bug didn't happen for me when it was uncompressed in my IDE. But after the compression/decompression cycle of committing/pulling, it's obvious that the code sometimes gets infected by the hard drives themselves. If you're in a silent room when you push to github, you can actually hear the alterations if you listen really, really hard.