The part I don't understand is how there are enough people betting on the temperature being normal on one specific day at CDG, that you can make that much money betting on it being hot.
I really need to figure out a better sandboxing method for shells. It's crazy to be things where my keys, browser data, shell history are all accessible.
I do try to use firejail where possible, but it's quite cumbersome. Every so often I look for tools to help with this, but everything is oriented around making a specific program (e.g. Firefox, steam) work.
Apps should permit people to use any device or operating system. Security shouldn't rely on client-side checks which can be bypassed. Apps forced to do this by regulations and industry standards should use this instead of the extraordinarily anti-competitive Play Integrity API.
Well said, but sad. I wonder what regulations they mean. Maybe industry-specific stuff? I'm not aware of anything that would force this for end-users.
A world cup with 48 teams, where fucking Curacao qualified. If you get invited because the president of the host country started a war with one of the participants, you cannot accept. That is shame you will never recover from.
Yeah, I'd say for information, certainly, but there are other ways you could be valuable. A dev on a popular open source project might be very valuable for executing supply chain attacks.
Still team Emacs. We're a team because we use elisp, not because of something trivial like how our text editors work.