651–660 of 793 posts
Earlier quoted context omitted.
Checks are still common in the good ole USA.
Common? maybe for seniors. I probably handle a physical check once a year.
It doesn't solve the current issue, but in case we don't manage to push back on this, some people might not know that there are various actual linux OSes for mobile: - SailfishOS: still linux based and seems fairly community inclusive, but the UI part of the stack is closed source. Is the only one officially allowed to run android apps, via emulation. Has existed for a very long time, it's lightweight and I think the…
Usability-wise, they are no match for Android and iOS—or even versions of them from five years ago. UI/UX is costly, and most FOSS projects cannot get it right without massive investments from enterprises (e.g., Red Hat's UX designers heavily contributed to GNOME) or startups (e.g., Zed, Element, Bluesky). Projects without that backing are mostly unusable, at least from a Gen Z perspective.
Earlier quoted context omitted.
You dont have the ability to guarantee you have overridden anything. The integrity of the OS cannot be verified and anything with root can lie to you that it was revoked. It does not put power in your hands. Installing your own build does wipe the device when you unlock the bootloader, yes, but updating it with a locked bootloader does not. It would be a one time transfer if you have official images already installed…
> Your paths forward are a false dichotomy. These are not the only 2 options. You can simply update your build with the changes you want. Okay, so once I install grapheneOS, how do I update it with my own custom build while keeping my data intact? > You dont have the ability to guarantee you have overridden anything. The integrity of the OS cannot be verified and anything with root can lie to you that it was revoked.…
Its not advisable to run anything as root, at all. Or expose access to it in any form.
You can make userdebug builds to access a form of root that doesnt undermine the entire security model, in ADB. Afaik this lets you access apps internal directories but is not recommended for production devices.
Earlier quoted context omitted.
Which phones are supported by which of these operating systems? And can you provide some relevant links?
- https://sailfishos.org - https://docs.sailfishos.org/Support/Supported_Devices They have few devices of their own (new one coming out this October) and they officially support many Sony Xperia devices. There are also many community ports. - https://ubuntu-touch.io - https://devices.ubuntu-touch.io They have 33 supported devices, some are being shipped directly with the OS or have an official agreement with the phon…
E.g., on the XPERIA 10 IV, the camera and mic doesn't work, which makes it hard to use as a phone:
https://forum.sailfishos.org/t/functional-state-of-the-xperi...
All talk, no solutions from F-droid. What are they actually doing to solve it? Why not stand up their own vetting system? I'd love some technical solutions, instead this is just childish.
By analogy, would complaining about any organization ridiculously more powerful than you (e.g. a government) without having a complete alternative ready to go also be "childish"?
Earlier quoted context omitted.
And all are useless because you can't use your mandatory bank or gov id app.
Not useless. It is like the missing printer driver for Linux Desktop. It makes the experience ugly, but this is not the fault of the Linux OSes. Also the bank should not require apps (instead they can offer hardware key support or desktop apps) and in fact some - at least in Germany - offer a different authentication possibility. Also the app for the German ID is published on fdroid and does not rely on Google servic…
I'm confident this is a very common experience worldwide, be it with gov IDs or banks.
Android users need to switch to Graphene. Someone needs to create a Linux based mobile OS foundation - Google's domination is contrary to many large companies interests, and if Meta and many other such companies were approached, they may well donate large sums of money in their own strategic interests.
AOSP is a Linux-based mobile OS. It runs fine on top of standard Linux kernels without downstream changes. Getting rid of the need for closed source userspace drivers for components like a modern Mali GPU can be done with AOSP and will benefit the most people that way. AOSP if many companies and others band together to do it. It could also happen due to government intervention due to Google's antitrust law violations, but that could be done poorly in a way that harms open source.
Earlier quoted context omitted.
> and they are legally allowed to fingerprint grapheneos and block Play functionality. No, and you also don't understand how the Play Integrity API is implemented. Google has a bunch of monopolies tied to Android. Antitrust laws put limits on what they're allowed to do which Google has been egregiously violating for many years. Google isn't legally allowed to pull a bait and switch with Android by changing it away fr…
giving the option to completely block attestation and DRM API would be a good start. > hardware attestation, which is not fingerprinting this is false, the attestation middleman Google server can fingerprint your unique device serial (in-silicon key) whenever it wants. the DRM situation is even worse as ANY app can fingerprint your device serial and I don't mean just the DRM ID. anyone who has a license server certif…
Earlier quoted context omitted.
It's because only Pixel devices have proper hardware security to build anything secure on top.
Hardware security is irrelevant to me. I just want to leave Google behind me. I do not want Google's hardware.
Earlier quoted context omitted.
We're still arguing for several reasons, one of them is that people still confuse the user with the owner, as you do. "The user must be able to override" is implies that if you have physical access to someone's phone, you can install a keylogger before handing the phone back its owner. Nice for you but I imagine the owner might still quibble, even if you quote TRON.
If I hand my windows laptop to someone, they can also install a keylogger. But no one said we have to copy that flawed concept. macOS and Linux already have a good solution, requiring your full unlock password in a privileged dialog to authorize changes. It's ridiculous that changing the settings on my device is protected 10× more than transferring all my money to a random person.
You use operating systems that have significantly worse security than GOS, iOS and even stock Android as your examples?
Also you literally are the owner with GrapheneOS, lacking security is not "full ownership." You can create your own build of GOS, you can modify it ahead of time, you can literally see all of the source code it's running.
Claiming GOS isn't true ownership is like complaining that you can't change your car's wheel alignment while driving it and saying it means you don't truly own your car.