this post was submitted on 19 Sep 2023
212 points (100.0% liked)
Technology
37757 readers
588 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think signed hardware components are actually a good thing. The problem is that Apple makes it so that unapproved hardware doesn’t work at all. I think the device should warn the user, but allow them to override and continue at their own risk.
Of course, Apple isn’t going to allow that unless they’re forced to. Glances sideways at the EU.
Yeah, it would be a fantastic thing if it showed a permanent history of parts and their serials in the settings, as well as a date on which the change was noticed, so you have an idea of the history of the phone and what's been replaced. And, of course, not locking you out of features.
With the healthy second-hand market for iPhones, that would be great. Let buyers decide how they feel about previous repairs, offer transparency.
The unhelpful move is requiring a connection to Apple’s servers to calibrate replacement parts.
Makes me wish Google hadn't canned phonebloks. Can you imagine how much waste we could have cut down on if we decided to standardize every component like the usb-c port?
I think we would need something like a Framework.
Project Ara had no future if all modules need a case for protection AND the components.
Phonbloks would never have worked. Phones are all different shapes and sizes, so you just run into tons of compatibility issues whenever you want to upgrade anything, as new components will be larger than the old ones. Technology just doesn't progress in ways that nicely fits into form factors from five years ago, fingerprint reader, FaceID, multiple cameras, wireless charging, etc. None of that fit into a block model. Phones are also a weird market place where people give up headphones and replaceable batteries if it makes their phone 1mm thinner, so a big bulky modular device would really have much chance against the much sleeker competition.
Fairphone is a much better compromise, it's modular and repairable, but in a way that is actually practical. Turning everything into LEGO blocks looks fun in concept images, but nobody would want to use that.
Moto Z is/was another more interesting approach, instead of making the phone itself modular, it has some contacts on the back to dock extension modules. So you get extensibility without really changing anything about the phone itself.
Sounds good, but how do you stop an unscrupulous repair shop from clearing the warning before the end user can see it?
If it is persistent but buried in settings, most people won’t notice.
Maybe the warning could require Apple sign-in to dismiss, but can be hidden at startup? Then make it an industry standard to present the phone when it is powered off.
EDIT: Yes, I know that this is still shitty for most customers.
Yeah, unfortunately that would be up to the average person knowing better than to give out passwords.