Readit NewsMore and more it seems people don't even find it necessary for that.
I'm "the Linux friend" for a lot of my friends, and over the last year-ish a surprising number of them have asked about advice for switching to Linux. I've helped four people attempt the switch, and three out of the four have stuck with Linux so far.
Apex Legends at least was running fine on Steam Deck prior to november 2024 when they instituted this change, and I can tell you from personal experience it had very little impact on cheaters, which was their excuse for the change (supposedly most cheaters were connecting via Linux clients).
Deleted Comment
The oldest iPhone OS that natively boots on my particular one is 1.1.4, 1.1.1 (which is the highest version number where you can trivially escape the OOBE via the emergency dialer) fails to initialise the FTL (flash translation layer), probably because the chip is sufficiently different from that used in the older phones.
It would bring me great joy to be able to relive emergency dialer hacktivation again, but I have lost that particular iPhone 2G, and only have this 16GB one left.
In my opinion, the fact that Apple is now selling a bag to carry your oversized phone around in, is an admission that they failed to make phones that are convenient to carry.
That "except" is doing a lot of lifting, in my opinion. Automatic Let's Encrypt is a big part of why I reach for Caddy. Install, run, done. No cert management headaches. It felt like magic the first time I used it, and now that I think of it, it still does.
Also, if I want to add another domain that should be accepted and reverse proxied to my application, in Caddy I just do this:
example.com wp.example.com caddyfreakingrules.example.com {
root * /var/www/wordpress
php_fastcgi unix//run/php/php-version-fpm.sock
file_server
}
Another thing, does nginx with the above configuration automatically load new certs if the ones that were there when the process spawned have since expired? Because not only does Caddy automatically renew the certs, it is handled transparently and there's zero downtime (provided nothing changes about the DNS pointers of course).
Caddy is freaking awesome!
Bonus, if this were your Caddyfile (the entire thing, this is all that's needed!):
{
admin off
auto_https prefer_wildcard
email hostmaster@example.com
cert_issuer acme {
dir https://acme-v02.api.letsencrypt.org/directory
resolvers 1.1.1.1 1.0.0.1
dns cloudflare {env.CLOUDFLARE_API_TOKEN}
}
ocsp_stapling off
}
example.com wp.example.com caddyfreakingrules.example.com {
root * /var/www/wordpress
php_fastcgi unix//run/php/php-version-fpm.sock
file_server
}
# This is simply to trigger generation of the wildcard cert without
# responding with the Wordpress application on all of the domains.
*.example.com {
respond "This is not the app you're looking for" 404
}
The result of which is that Caddy will only generate one cert for the above 3 sites, and Let's Encrypt won't leak the existance of the wp.example.com and caddyfreakingrules.example.com domains via certificate transparency.
Manufacturers should feel free to offer updates. If the user feels the tradeoffs make sense, then they should be free to accept updates. But this business where the manufacturer thinks they are somehow entitled to mess around with a product you've already purchased from them has got to end. It's not their product anymore, it's yours.
Also, adding features on its own is great, but obviously stuff like what happened here can't be allowed to happen, and those Samsung or LG smart fridges that became advertising boards is obviously also not acceptable...
Easy to call the bullshit out, hard to actually define the responsibilities of a manufacturer in a law.