![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
apt dist-upgrade will sometimes resolve this.
apt dist-upgrade will sometimes resolve this.
Yes, but it’s a bit weird and the interface isn’t designed for it. I keep them separate, but I could see it being useful in a pinch.
God forbid you try to look good for your wife 🤷
If you’re running Safari, you’re already running their OS. If Apple wants to spy on you, they’ve already got the means to do so, so you’ve already decided to trust them.
Switching to Chrome or Firefox means trusting one more entity in addition to Apple. This expands your possible exposure.
Also using duck typing fails against php is pretty funny when it’s being compared against JAVASCRIPT of all things.
Hashing on the client side creates a “pass the hash” vulnerability. What you’ve done in that case is made the hash itself the password, because that’s all the client needs to pass to the server to authenticate. This means that if those hashes are leaked, they can be immediately used to access the server instead of being cracked first.
Apple hit a sweet spot with this. x86_64 applications run at acceptable speed (making the transition easy for people who buy the hardware) while not being SO good that there’s zero reason for developers to start porting their software.