I mean I already knew something was weird when I couldnt su into root and do... root things without a bios hack on a Mac. Thats just not how Unix works at all... The whole concept of root is you are root no exceptions.
> The whole concept of root is you are root no exceptions.
Wait until you learn about mandatory access control [0] ...
Apple seems to do all kinds of weird networking _stuff_. For instance, during wakeup, your T2 equipped Macbook will wait for a DNS response and then use said DNS response to synchronize time via NTP before letting the user use the keyboard. Probably checking timestamps on signatures for the keyboard firmware, or something stupid like that. This only happens if it happens to have a default route. Similarly, all macOS…
Holy cow, you just explained a load of weird keyboard behavior I was seeing after waking from sleep.
I'm seeing this weird keyboard behaviour on wakeup with my 2012 MBP running Catalina too
What's the alternative for the typical user? Windows has its own problems, and let's face it: market forces on this sort of thing or any other practices by the two of them have not driven people to use desktop Linux instead. For most people, there's simply no reasonable option to switch to that would avoid these things or employ market forces to get these companies to change their ways.
I installed GNU/Linux for my relatives and it's been working fine for years. So I would say GNU/Linux is a perfect alternative for typical users.
This assumes that your software is doing what you asked it to do, not what some bigco or malware wanted it to do.
firewall anything that doesn't go through your DNS server... at least thay way the malware will be obviously detectable.
But DoH is just any other HTTP request. This is the downside of networks blocking everything except 80/443 outbound and browsers not supporting SRV records.
Apple seems to do all kinds of weird networking _stuff_. For instance, during wakeup, your T2 equipped Macbook will wait for a DNS response and then use said DNS response to synchronize time via NTP before letting the user use the keyboard. Probably checking timestamps on signatures for the keyboard firmware, or something stupid like that. This only happens if it happens to have a default route. Similarly, all macOS…
When I had the authenticate with watch option enabled, and for some reason the watch lagged, the Mac didn't allow me to log in with my password or finger.
Tim Cook's Apple Inc is really a nightmare. Sure we have sleek shiny laptops and devices that are amazingly powerful but at what cost? I still haven't found a trackpad as good as MagicTrackpad sadly otherwise I'd ditch the MacBook Pro. To be fair to Apple though, it's their OS, they can do what they want and we agree every time we update MacOS or iOS. It's crazy to me that we basically only have 3 phone device choice…
Would you use a good trackpad that connects via USB or bluetooth? Its a real question because I see a lot of comments about people not leaving the Macbook because of the trackpad even though they dislike the rest of the laptop? Seems like something that could be a product?
The trackpad is just the saillant point.
As we(I) go deeper the "let's try linux" route, thousands more papercuts come to the surface. It's fine for specific use cases (e.g. just focusing on backend dev), it becomes worse for wider use cases.
Apple seems to do all kinds of weird networking _stuff_. For instance, during wakeup, your T2 equipped Macbook will wait for a DNS response and then use said DNS response to synchronize time via NTP before letting the user use the keyboard. Probably checking timestamps on signatures for the keyboard firmware, or something stupid like that. This only happens if it happens to have a default route. Similarly, all macOS…
> but is it really that hard to document these behaviors? I imagine it is, given the bureaucracy of a big company. Apple's documentation has long been really dreadful, mostly nonexistent and where it does exist, usually incomplete and even wrong. I've assumed it was because the code itself is developed by isolated groups while the documentation presumably has to touch all sorts of people (publishing, translation, lan…
Makes one wish Woz’s Apple was still around (and yes I know Jobs tried as hard as he could to put a monkey wrench into that at the time)
> bringing the OS layer under their complete control To me, it seems the purpose is almost always to protect the average user from malware. What do you think their reasoning is?
So what if that is their reasoning? Freedom also means the freedom to make mistakes. We don't set a standard of "absolute safety" in many other (arguably more important) areas of our lives, so why do it here?
Because a computer is an appliance for most people, with it working, and it being secure, being an absolutely critical feature.
I believe still have the option to disable SIP and make as many mistakes as you want. [1]
>Options are limited No not really, but limited is the mindset of peoples.
>No not really, but limited is the mindset of peoples. I'd argue options really are limited. Your counter argument assumes one can just roll their own OS with the same features and functionality as current-gen OS's. That's quite a leap. Options today are Windows, Mac, or some flavor of Linux if you can get it to work. Linux aside, Windows and Mac both are making it so you no longer own the OS but are "subscribed" to…
> or some flavor of Linux if you can get it to work
Do not try to get anything work. Just buy preinstalled.