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

You can still do this if you use https://www.shodan.io/

It’ll let you find IoT devices and cameras connected to the internet if you know what to search for and an alarming amount of them are locked behind an admin/admin login.

I advise against nosying around because there’s a near 100% chance that it’s illegal to do so in your jurisdiction.

Oh wow, they really closed it down huh?

Not too long ago you were able to change it.

This dumbing things down to prevent customers from fucking themselves over and using up CS resources is getting ridiculous.

Say you need to change some settings but your modem/router isn’t online then you’re SOOL.

Cox, who uses the same gateway, is even worse. They won’t even allow you to enable legacy mode (802.11b) for IoT devices that cheaped out on WiFi cards, not even on a separate network and their customer service can’t enable it either.

I dread moving into a Cox region where there’s no fiber competitor available.

Agreed.

Hold them in contempt of court and let them spend a week in jail all expenses paid.

They’re just trying to run out the clock so that, come election time, they’ll throw their hands up in the air and go “Welp, guess we’ll have to use the old map”.

Having a special master draw up a map is great in theory, until SCOTUS stays the lower ruling and drawn map and decides to not rule on the case until after elections (if they even were inclined to rule in favor of a fair map to begin with).

Cue the nuclear shills that will handwave away any legitimate concern with wishful thinking and frame the discussion as solely pro/anti fossil, conveniently pretending that renewables don’t exist.

ETA:

Let’s look at some great examples of handwaving and other nonsense to further the nuclear agenda.

Here @danielbln@lemmy.world brings up a legitimate concern about companies not adhering to regulation and regulators being corrupt/bought *cough… Three Mile Island cough*, and how to deal with that:

So uh, turns out the energy companies are not exactly the most moral and rule abiding entities, and they love to pay off politicians and cut corners. How does one prevent that, as in the case of fission it has rather dire consequences?

So of course the answer to that by @Carighan@lemmy.world is a slippery slope argument and equating a hypothetical disaster with thousands if not millions of victims and areas being uninhabitable for years to come, with the death of a family member due to faulty wiring in your home:

Since you can apply that logic to everything, how can you ever build anything? Because all consequences are dire on a myopic scale, that is, if your partner dies because a single electrician cheaped out with the wiring in your building and got someone to sign off, “It’s not as bad as a nuclear disaster” isn’t exactly going to console them much.

At some point, you need to accept that making something illegal and trying to prosecute people has to be enough. For most situations. It’s not perfect. Sure. But nothing ever is. And no solution to energy is ever going to be perfect, either.

Then there’s the matter of misleading statistics and graphs.
Never mind the fact that the amount of victims of nuclear disasters is underreported, under-attributed and research is hampered if not outright blocked to further a nuclear agenda, also never mind that the risks are consistently underreported, lets leave those contentious points behind and look at what’s at hand.

Here @JohnDClay@sh.itjust.works shows a graph from Our World in Data that is often thrown around and claims to show “Death rates by unit of electricity production”:

Seems shocking enough and I’m sure in rough lines, the proportions respective to one another make sense to some degree or another.
The problem however is that the source data is thrown together in such a way that it completely undermines the message the graph is trying to portray.

According to Our World in Data this is the source of the data used in the graph:

Death rates from energy production is measured as the number of deaths by energy source per terawatt-hour (TWh) of electricity production.

Data on death rates from fossil fuels is sourced from Markandya, A., & Wilkinson, P. (2007).

Data on death rates from solar and wind is sourced from Sovacool et al. (2016) based on a database of accidents from these sources.

We estimate deaths rates for nuclear energy based on the latest death toll figures from Chernobyl and Fukushima as described in our article here: https://ourworldindata.org/what-was-the-death-toll-from-chernobyl-and-fukushima

We estimate death rates from hydropower based on an updated list of historical hydropower accidents, dating back to 1965, sourced primarily from the underlying database included in Sovacool et al. (2016). For more information, see our article: https://ourworldindata.org/safest-sources-of-energy

Fossil fuel numbers are based on this paper which starts out by described a pro-nuclear stance, but more importantly, does a lot of educated guesstimating on the air-pollution related death numbers that is straight up copied into the graph.

Sovacool is used for solar and wind, but doesn’t have those estimates and is mainly limited to direct victims.

Nuclear based deaths is based on Our World in Data’s own nuclear propaganda piece that mainly focuses on direct deaths and severely underplays non-direct deaths.

And hydropower bases deaths is based on accidents.

So they mix and match all kinds of different forms of data to make this graph, which is a no-no. Either you stick to only accidents, only direct deaths or do all possible deaths that is possibly caused by an energy source, like they do for fossil fuels.

Not doing so makes the graph seem like some kind of joke.

Most doxxers don’t technically release the information, rather they’ve acquired it and point others to where they’ve acquired it or simply disseminate it further.

That’s what I’m saying. In most cases the doxxer isn’t the one who originally provided the info, but rather someone who has found the information online via a Google search or something similar.

Only if there’s a risk at incriminating yourself, and if it’s not immediately apparent how you’d run that risk (e.g. you’re a witness that doesn’t have a direct relation to the crime at hand) you’d have to motivate how it could be incriminating.

Isn’t that a little bit of circular reasoning?

If I doxx someone online then it gets indexed by Google, if someone then Google’s the information it stops being doxxing?

I’d assume most doxxing isn’t done by someone who has unique firsthand knowledge (e.g. “Oh I know John, he lives on so and so road”) and instead is done by finding the information online whether via Google or a different public source.

At least in the US, where a ridiculous amount of private information is deemed “public”.

There are plenty of instances that are open, but it depends on your definition of “censored” if they are what you seek.

Completely “uncensored” instances are rare if not non-existent because most instances will at least try to adhere to the laws of their jurisdiction and in addition will have some rules in place to keep things running smoothly and pleasant for everyone.

Most big instances are run from the EU so they’ll often have rules regarding hate speech.

Depending on your definition your only options might either be Japanese instances due to less strict laws around certain content or right wing instances, but both will be almost uniformly blocked on other instances.

It means no porn, how much that overlaps with anything remotely considered NSFW is up to the admin and you’d have to ask them.

The individual cashier won’t care, but the manufacturer might, especially if they’re returned as defective because they then make their way back as RMA.

Shops will also stop stocking the item if it stands out because more people return them.
They want to make a profit after all and if they have to discount items as “open box” then they’re losing out on profit, especially since the margins on some of these are already pretty low for retailers.

Typically low level attacks such as these is where it starts because they grant access to parts that can be used to learn more about the system as a whole.

This understanding then can be used to find easier to exploit avenues.

A good example of this is the history of exploits on Nintendo hardware.

They almost all started with finding an exploit at the hardware level, which then subsequently lead to finding software exploits and ways to leverage them in an easy way for end users.