Why not simply boycott what you dislike?
As for me, compressed scores are no fun. Code golfing was always about the size of source code, and nobody writes compressed code. You could do that with any programming language (achieving a far better compression ratio for most), but nobody ever did it, because it adds some randomness to the challenge: A better golfed version in terms of shorter source code can be overtaken by lazy code, which happens to compress better.
On the other hand, it's difficult to forbid that. Where is an exact border between compression and some other golfing language tricks? Those rely to a certain degree on commands that can to some extend be seen as a couple of instructions "compressed" into a single byte. I still like it because you can do clever golfing tricks with them.
For myself, I decided not to upvote answers like that. For answers to my own questions with cleverly golfed source, but compression flag, I plan to comment that I will upvote the uncompressed version (unless the author can explain some brilliant ideas how this was designed for better compressability – unlikely to happen).
I invite you to join this way to handle it. Don't cheer a doped athlete.