All the damn developers keep turning off online play for Linux users though... I play two games a lot currently, Apex Legends and Battlefield 6, both block Linux players from online play thanks to their shitty kernel rootkits not supporting Linux.
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).
> supposedly most cheaters were connecting via Linux clients
I always find this so hard to believe, mainly because the majority of players are on Windows, which means that the market for cheats is there and statistically most likely to happen there.
I just don’t play games by devs that snub Linux. There are many to choose from.
The thing with Linux cheats is that they were significantly easier to make(you didn't have to think about bypassing the anticheat at all, you could just read the game's memory or LD_PRELOAD your cheat in), and a lot more were publicly available(in true FOSS fashion, a lot of Linux cheats were open-source). A cheat that could cost $30-$60 a month on Windows could be free as in freedom(and free beer) on Linux.
I'm sure the number probably changed a bit, but I can tell you for a fact it isn't like cheaters disappeared overnight just because they banned Linux clients.
Fascinating. Could this method be used to boot iPhone OS 1.0 (or at least 1.1.1) on an iPhone 2G with 16GB NAND maybe?
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.
I wish the iPhone 12/13 mini had been a few mm thicker for a bigger battery, and had been in the Pro class of devices. As it stands they didn't have a good enough battery to last a day, and most people interested in smaller devices had probably just picked up the new SE that was released just half a year earlier.
I believe the issue is that with Jobs gone, Apple's design team is now apparently unable to continue their job. Instead of developing their own UI paradigm for small screens, they keep copying from Google Pixel both the UI ideas and the screen size. And now that they ran out of useful ideas, they turned everything transparent. Why make the iPhone look more like Apple Vision when people so obviously hate the latter? [1]
My prediction is that the age of AI and LLM assistance will make tiny devices the norm. Like those AI pins. Like Siri inside AirPods. Like Meta's AR glasses. But it seems that Apple is losing the race here. They lost their edge when it comes to developing new user interface paradigms.
>Apple's design team is now apparently unable to continue their job
Honestly id say this is a mix of both Jobs and Ive being gone.
Now under the operational maximalist that is Tim Cook, they just revert to old designs every few years and call it revolutionary. See: edges on the iPhone. First, rounded edges. WOW, revolutionary! Then a few years later, hard edges. WOW, revolutionary! Then a few years later, rounded edges. WOW, revolutionary! Then a few years later, hard edges. WOW, revolutionary!
All the while stripping actual functionality out of the devices and removing useful features like headphone jacks. There hasn't been real product innovation at Apple in over a decade.
The most important thing Jobs did (and he mentioned this) is to say No to great ideas. Like this, like iPhone Air, like Apple Vision Pro, etc.. Apple without Jobs is now much like it was before Jobs in the 90s, only this time it has a lot more momentum than it had before. Still though Apple is back to throwing shit at the wall to see what sticks.
As someone who's spent a while playing with one (that I didn't buy) and who hasn't picked it up off the shelf in months:
I don't think most users were returning it because they hated the UI or even the device in the usual sense. (There are certainly issues I could detail, but they don't feel like the core problem).
The core problem is just that it just doesn't really....accomplish anything.
Once you get past treating it like an expensive Google Cardboard ("neat tech demo") - it's very hard to figure out what the point of the thing is. What problem does this actually solve for you/what thing is it actually better to use this for than other existing solutions.
Extremely high price tag with no "killer app"/function that makes anyone who tries it "get it" quickly and want one, is a pretty impossible sell.
Right, in the nginx example above, someone has setup a secondary tool to provide certs at the location referenced, and is also handling renewal of them.
Also, if I want to add another domain that should be accepted and reverse proxied to my application, in Caddy I just do this:
Suddenly not only does my Wordpress site respond on example.com, but also wp.example.com, and caddyfreakingrules.example.com, Caddy will fetch and automatically rotate certs for all three domains, and Caddy will auto-redirect from http to https on all three domains. (Does the ngnix example actually do that?)
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
}
Then you'll disable the unauthenticated JSON API on localhost:2019 (which is a good security practice, this is my only gripe with Caddy, this API shouldn't be enabled by default), tell Caddy how to use the DNS-01 ACME resolver against Cloudflare (requires a plugin to Caddy, there are loads for many DNS providers), and then tell Caddy to use appropriate wildcard certs if it has generated them (which for *.example.com it will have).
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.
Problem with that is that if it's an online product then the manufacturer also _must_ provide updates to keep the device secure so that it continues to do whatever they sold you in the first place.
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.
The manufacturer must offer updates to keep the devices secure, but it should never be able to force those updates onto already-purchased devices. The choice should always be with the user.
I don't disagree, but if we end up in a situation where users are negatively affected because they chose not to update for fear of shit like this happening, that's not a great position either.
All the electrical steering columns designs I've seen have used redundant sensors (often groups of them) specifically for that reason. The physical steering wheel to the shaft is still a SPOF, but it's also a "dumb" part where the only failure cases are mechanical. Eliminating failures there is straightforward engineering.
Yeah, I should have spent an extra 10 seconds thinking of the problem here and I'd have realised you can have multiple sensors going to different software on one steering column...
I remember DSL had a window manager that would allow you to merge applications into tabs ... it's nice having only one window ... I reminds me of the 50 MB operating system days. Except this time the browser doesn't suck ... I can't believe I'm watching youtube cat videos in iterm2 \m/
Teenagers figure out how to hack locked down consoles, which are hostile to make money.
All it will take is someone to make a fediverse chat that can be simply stuck on a Pi from a premade image, and automatically runs a script to update the DNS with their IP and the kids will do it.
Someone will make it easier. All the stuff you use today used to be a lot harder and more complicated than it is now. People worked to take the difficulty off, usually because they wanted to do the same thing and the difficulty annoyed them.
It kinda is but I didn't want to make that assumption. That is what I had assumed, for what it's worth. (Actually, I figured it was either knowledge or resources.) It also helps for the reason to be given explicitly so others can weigh in with relevant arguments rather than one that refutes something you didn't mean.
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).