• 8 Posts
  • 1.29K Comments
Joined 3 years ago
cake
Cake day: June 11th, 2023

help-circle


  • I haven’t found anything I want to install on my iPhone that I can’t. At one point it was emulators

    So you have found something you wanted to install on your iPhone that you couldn’t, but Apple has decided to allow it for now. I think it’s pretty obvious how this is a problem.

    Of course you’re not going to find apps that exist that you can’t install because Apple says so. People won’t bother making them if they can only be distributed to the tiny handful of users with jailbroken devices. Of course it comes up on occasion when Apple withdraws permission, with ICEBlock being the recent socially important case.


  • Way I see it, my iPhone is a pocket version of my Mac.

    The thing is, you can install software from whatever source you like on your Mac. That’s not true of your iPhone - even in the EU and Japan where they’ve been forced to open up a little, apps can only be installed with Apple’s permission.

    Macs were completely open in that regard until recently. You could install apps from wherever you want. Now, Mac apps have to be notarized by Apple or installing them requires use of the command line. That’s obnoxious, but the user still has the final say, unlike the iPhone.



    • Google has announced that a workflow for advanced users to install whatever they want will remain, but hasn’t published details. Many people don’t entirely trust them about this.
    • Third-party Android builds like LineageOS won’t be affected. These need a device with an unlockable bootloader. They can run any Android app that doesn’t intentionally sabotage them (some banking apps do this).
    • Linux distributions for phones exist, and can run Android apps via Waydroid. This provides the most freedom for the user, but the highest effort. This is mainly suited for Linux hobbyists right now.











  • Signal uses reproducible builds for its Android client, and I think for desktop as well. That means it’s possible to verify that a particular Signal package is built from the open source Signal codebase. I don’t have to trust Signal because I can check or build it myself.

    If I don’t have extreme security needs, I don’t even have to check. Signal has a high enough profile that I can be confident other people have checked, likely many other people who are more skilled at auditing cryptographic code than I am.

    Trusting the server isn’t necessary because the encryption is applied by the sender’s client and removed by the recipient’s client.