Sounds about right. Yes, I've been doing it for decades now and besides telling you who's selling email lists, it makes filtering much easier. Filtering by To: is pretty low effort compared to Bayesian spam filters etc. They get tossed in a Sieve filter as soon as they become a problem, and I'll send a bitch letter to the leaker with another random email address to see how dedicated they are to screwing me.
Most Linux kernel development is done by people affiliated with US companies, often by employees on company time. Linus moved to the US a long time ago, and the Linux Foundation is based in the US.
> Since the old version of the game is known on both sides, we compress the new version using the old version as its dictionary.
That's quite clever!
> Since we compress once and decompress many times on player machines, we can afford slow compression times. Zstd lets you tune the compression level, and we found that level 19 yielded about 13% better compression than zip.
Zstd is parallelizable across threads, which wasn't mentioned here. It helps speed it up at high compression levels, though not as much as I'd like.
I guess I'm so paranoid that not only do I run GrapheneOS, I've never had nor wanted banking nor payment apps on my phone. Having ALL my money be accessible from something so easily lost, stolen, or seized would be a constant source of stress for me. There's (hopefully) a lot of security around accessing it, but sometimes the only winning move is not to play.
https://en.wikipedia.org/wiki/Canary_trap
reply