USPS’ website does this, sort of.

If their text service is down it’ll let you know and just skip the 2FA process even though normally they offer an option to get the code via email.

The fact that they do this is bad enough, the fact that this happens so often that I’ve seen this at least a dozen times is even worse.

For one it’s just technicalities for another it’s the distinction between a company going out of their way to block repairs or a company just not caring and mainly focussing on their own repair process.

There are a couple of concerns with biometrics.

The big one is, as you already mentioned, spoofing biometrics.

The FaceID or TouchID sensor essentially saying “I got that face/fingerprint that you have in your Secure Enclave”. Granted it is a sophisticated attack, but nevertheless one you’d want to prevent if only because it’s good practice to maintain a secure chain in which the individual links can trust each other.

For similar reasons the lockdown mode exists, which is mainly useful in limited scenarios (e.g. journalists, dissidents, etc).

On the other hand, if ever there was a potential attacker, it would be a government because they unlimited funds in theory and it isn’t hard to imagine the FBI trying to utilize this in the San Bernardino case if it was available.

A different risk, which would make the above quite a bit easier to accomplish, would be an altered biometrics scanner that, in addition to working the way it’s supposed to work, stores and sends off your biometrics or simply facilitates a replay attack.

Lossless is understood to have a bitrate of at least 1411kbps, or about 1.4Mbps.

Theoretical sustained bandwidth capability of Bluetooth on the 2.4Ghz spectrum is 1Mbps, but in practice it’s a chunk lower in part due to overhead.

Even if we assume if you could just cram a higher bitrate through a smaller bandwidth (spoiler, you can’t), everyone would be up in arms about Apple lying about lossless and class action suits would ensue.

That said, you can’t. This is not like your internet connection where you’ll just be buffering for a minute.

As for what is and isn’t perceptible, I think you’re mixing up your tonal frequencies with your bitrates here.

Honestly the most frustrating part is that there is plenty to criticize Apple on, so there’s no reason to get caught up in fabricated clickbaity nonsense.

But instead of focusing on genuine concerns, people would rather hop on some misinformation train.

All the while, if you espouse opinions that are bit more nuanced than “Apple bad”, then you must be a bootlicker like you said.

It’s as if people are more concerned about missing out on joining the hype and showing off their armchair skills, rather than exercising a modicum of critical thinking.

Obfuscating what you have to do ≠ not providing you with a roadmap on what you have to do.

If they didn’t obfuscate it there would be many tools out there already to let it be done.

This is a non sequitur.

It doesn’t automatically follow that a lack of tools means there is obfuscation. The simple fact that there can be many reasons why tools aren’t widely available alone breaks that logic.

But I’d say the fact that we already know exactly why difficulties arise when replacing parts, definitely proves that there’s no obfuscation.

Which again circles back to the difference between anti-repair and not pro-repair.

Just because Apple doesn’t go out of their way to provide a roadmap and hold your hand and as a result you are having difficulties when you’re trying to do it yourself, doesn’t mean they are actively thwarting you.

Apple doesn’t even think about you and me, their concern is to facilitate their own repair processes.

They literally serial lock almost half of their parts.

They don’t.

Aside from biometrics none of the parts are serial locked.

What you’re thinking about is parts based factory calibrated data loaded into the parts from a central database.

Just because the system ignores the calibration data once the part doesn’t match the one the calibration was intended for, doesn’t mean it’s “locked”, it just means that you’re trying to use calibration data for the wrong part.

Dude has reverse engineered pretty much the entire hardware stack of Macs to be able to provide the global community with Asahi, but because he says something you disagree with he’s supposedly “uninformed”.

Talk about childish…

I’m not sure if you’re serious or trying to be sarcastic.

Bluetooth and WiFi are two different things.

For starters standard Bluetooth operates on 1MHz wide channels, BLE on 2MHz wide channels, whereas WiFi (nowadays) operates on 20 or 40 MHz wide channels.

Modern Bluetooth (on 2.4Ghz) can theoretically do bursts of 2Mbps, but in practice even 1Mbps is hard to hit in a sustained fashion.

2.4Ghz is just a frequency band and is not the same as bandwidth.

You might as well argue that a pickup truck and a formula 1 race car should be able to reach the same top speed in the same time because their wheel distance is the same.

I think […]

Think again

Good for them, but this whole clickbait nonsense about Apple “locking” things is just that, nonsense.

Hector Martin, creator of Asahi Linux said it best so instead of repeating his words I’ll just leave a link to his comments on the matter: https://social.treehouse.systems/@marcan/110803356645502548