• 42 Posts
  • 258 Comments
Joined 7 months ago
cake
Cake day: February 10th, 2024

help-circle


  • no long-term OS support

    IMHO, we need well-enforced laws requiring manufacturers to do both of these things:

    • Provide service manuals and reasonably priced parts for a sensible period, much like existing requirements for replacement car parts. (Perhaps 5 or 7 years minimum?)
    • Put into escrow all the information needed for community support of these devices, to be publicly released when the official support period ends. (The easiest way to satisfy this might be in the form of source code, but data sheets and API documentation could suffice if they are reasonably complete.)

    Some people have argued that the second point is impossible because phones are made with components that don’t come with specs or source code themselves. That might be true today, but if large economies start requiring it, then those component manufacturers will either fall into line or lose the market to competitors who do meet the requirements.

    and not easy to load an alternative OS on.

    This is another big one. We need to be able to unlock our bootloaders, install an OS of our choice, and re-lock our bootloaders. (Without permanently disabling any of the hardware features; there must be a way to fully revert to stock.) The only major brand smartphones I know of with a reputation for doing this right are from Google, which is kind of embarrassing.







  • All of those things are implemented in modern Android.

    No, they are not all implemented on any version of Android that I’ve seen. I don’t know about iOS.

    Well, almost.

    Right. We don’t need just a few pieces of what I listed. We need them all.

    an OS popup asks you if you want to give the app permission to use the feature.

    That’s not a bad interface, but it doesn’t address what I wrote: Individual control.

    Why should email address, sexual orientation, and home address be lumped all together into a single permission? Lumping installed apps and search history together isn’t much better. Why should a music player, which obviously needs access to music files, be also granted access to biometric data like voice recordings?

    This is impossible? The OS can either let the app use the mic or not,

    Of course it’s possible. The OS can record the file and then hand it off to the app. No microphone access required.

    Android always shows a green indicator on screen (upper right corner) when any app is using the microphone

    That alone is better than nothing, but not enough. How is a user to know if something was captured when the screen was off?

    These things are indeed improving as new versions come out, but at a glacial pace. Heck, it was ages before Android stopped letting apps spy on each other’s log messages. It’s now at version 15 and still doesn’t have basic controls like restricting network access.





  • Pretty sure that qualifies for that permission.

    I don’t know what you mean. Existing behavior does not provide the control or visibility that I described.

    One important difference is that the “permissions” in the screen shot are effectively all-or-nothing: if you don’t agree to all of them, then you don’t get to install the app. They’re not permissions so much as demands.

    (Some OS do have settings that will let you turn them off individually after installation, but this is not universally available, is often buried in an advanced configuration panel, leaves a window of time where they are still allowed, and in some cases have been known to cause apps to crash. Things are improving on this front with new OS versions, but doing so in microscopic steps that move at a glacial pace.)


  • if you record a video with sound, then the FB app has to have permission to record your audio.

    I can’t tell if you’re trying to explain how it currently works (which I know very well, thanks) or asserting that the current behavior is necessary in order to record with sound.

    It really doesn’t have to be as it is. The OS can provide a record-video API, complete with a user-controlled kill switch and an activity indicator, and the app can call it. The app doesn’t need direct access to the microphone to allow the user to create a file with sound.

    Edit to clarify: I’m not saying that the “permission” doesn’t work as advertised. I’m saying that recording an audio file doesn’t have to require a permission system as coarse and disempowering to users as it is today. I guess the people clicking the downvote button misunderstood.