• 4 Posts
  • 477 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.




  • I’ve used several iterations of Gnome, several iterations of KDE, Mate, Cinnamon, Hyprland, XFCE, LXDE, Fluxbox, and several other things I can’t be bothered to remember. I can be productive on any of them given some time to set them up.

    I do have preferences though, and I like KDE on a laptop/desktop and Gnome on a tablet. I just wish Gnome would do something about its horrid onscreen keyboard.



  • 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.



  • Let’s clarify some terminology.

    Android is an operating system, not hardware. Android uses the Linux kernel, but differs greatly from desktop-oriented Linux distributions. Most phones are designed for Android, a bit like most PCs are designed with Windows in mind.

    Desktop-oriented Linux distributions have a semi-standardized software stack with Linux, GNU libraries and utilities, a shell, X11 or Wayland, some sort of window manager or desktop environment, etc…

    Other comments have explained how the hardware makes it difficult to have generic operating systems that install easily on any phone like we do for PCs, but they do exist. Ubuntu Touch and PostmarketOS are examples of desktop-like Linux distributions for phone hardware. It’s possible to install and use these on certain phones, but there’s usually a feature or two without a working hardware driver. Desktop Linux on laptop computers used to be that way too, but far fewer laptops have missing drivers now than a decade or two ago.

    I have PostmarketOS installed on an older phone. I don’t think the user experience is quite ready for most people to use as their primary phone, even for me, and I’ve been running Linux on laptops for most of my adult life.





  • I wonder what an alternate history where Google chose not to become evil would look like.

    What if they had looked at Microsoft’s Palladium proposal and thought, as pretty much everyone outside institutional IT departments did that locked devices with remote attestation was a nightmare scenario best forgotten, refused to build it, and made an effort to prevent anyone else from doing so on top of Android? Safetynet didn’t appear until 5-6 years after Android launched to the public. What if it never did? Android already had enough momentum by that point I don’t think the financial sector could refuse to be on it no matter what risk management said.



  • Pixels have a pretty strong warning on boot for unlocked bootloaders and an easily-typed URL with a detailed explanation.

    That seems like enough to me from the manufacturer side. Of course I can imagine someone ignoring the warning; people sometimes climb into tiger enclosures with predictable results, but it shouldn’t be on device manufacturers (or zoo management) to prevent all possible negative outcomes.