Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Your phone is about to stop being yours

keepandroidopen.org

Post reply on HN
Print view View original

191–200 of 927 posts

Re: Your phone is about to stop being yours

#191

Post by ryandrake »

Anonyneko wrote: post #133

I've resigned to the fact that I'll need to use two phones, one with locked down Android/iOS for banking applications and government services (those require strong bank ID around these parts), another with some kind of a Linux or unlocked Android for literally everything else. Oh well, such is life, most people don't care enough about this to pressure Google/Apple/banks/governments into yielding. A big reason why a n…

What we need to push back on is making a phone a requirement to do routine banking and conducting other necessary business. There is no reason I should be required to have a phone in order to query my balance or transfer money to someone, when I have a perfectly good computer sitting here.

Re: Your phone is about to stop being yours

#192

Post by dylan604 »

quantumleaper wrote: post #184
brandonhorst wrote: post #176

Earlier quoted context omitted.

This is not true, running your code on your phone with Xcode has always been free.

With a free account, it needs to be reinstalled every 7 days because the signature expires. It's hardly convenient for personal use.

[flagged]

Re: Your phone is about to stop being yours

#193

Post by pocksuppet »

muwtyhg wrote: post #182
gslepak wrote: post #153

Earlier quoted context omitted.

Or choose freedom. I've been enjoying GrapheneOS for a couple of years now and recommend it.

Do you run into issues with apps not supporting it? Things like banking or auth? That is the main complaint I see for alternative phone OSes, and I don't know if that has gotten any better.

My bank detected someone logging in with my password from a GrapheneOS phone and made me change my password and scan my face. That was dumb.

With that out of the way, and the device now seemingly authorized, it still doesn't work, because when I log in, the app restarts. That could be a real compatibility problem.

Re: Your phone is about to stop being yours

#194

Post by pocksuppet »

catlikesshrimp wrote: post #129
rootusrootus wrote: post #115

Earlier quoted context omitted.

If you are stuck in a walled garden either way, might at least try to get the benefits of it.

Includes status symbol and ecosystem lock!

So does Android, but without the status symbol, the high res screen, or the integration with your laptop.

Re: Your phone is about to stop being yours

#195

Post by kube-system »

anoncow wrote: post #155

Our phones stopped being ours ever since we accepted phones with locked bootloaders. I hope Android and iOS both disappear. Trading freedom for security has resulted in what we knew would happen.

Lockable bootloaders are the best of both worlds.

Re: Your phone is about to stop being yours

#196

Post by therein »

dylan604 wrote: post #192
quantumleaper wrote: post #184

Earlier quoted context omitted.

With a free account, it needs to be reinstalled every 7 days because the signature expires. It's hardly convenient for personal use.

[flagged]

It happens. Sometimes you're done making updates to a personal app you use that you wrote.

Re: Your phone is about to stop being yours

#197

Post by cestith »

code_duck wrote: post #132
Xunjin wrote: post #16

Let me play out a scenario, imagine to use a Desktop Hardware like a complete built rig, you would need a specific OS like Windows 11 and you could not run Linux on it, just because it's a vendor lock-in. Why is this acceptable for phones but would not for the case above? I know a lot of people don't care, and that's ok, but we should root for an open choice for the users.

It’s the same situation as game consoles. Custom built hardware that is only meant to run the one specific vendor OS. There have been many other computing devices like that in the past as well. The general purpose desktop computer that allows a choice of operating systems is actually less common than the other way. Historically, people didn’t expect to run alternate operating systems on a mainframe, 80s and 90s compu…

That’s odd, because I remember being a user of MUSIC on the university System/360. I imagine it also sounds odd to all those people who ran AT&T Unix on their PDP/11 systems instead of a Digital OS like RTS/11. Or the people who ran Xenix on their PCs. Or the folks like me who installed OS/2 on what was sold as an MS-DOS machine. Then there were the folks who ran A+ on their Atari.

Re: Your phone is about to stop being yours

#198

Post by AnthonyMouse »

dylan604 wrote: post #192
quantumleaper wrote: post #184

Earlier quoted context omitted.

With a free account, it needs to be reinstalled every 7 days because the signature expires. It's hardly convenient for personal use.

[flagged]

Every 7 days, forever?

At some point you have the thing working to your satisfaction and just want to continue using it.

Re: Your phone is about to stop being yours

#199

Post by ziml77 »

advael wrote: post #91
kodablah wrote: post #65

Earlier quoted context omitted.

> Saying there is no opt-out is just false I can't see where one can opt-out of this new behavior and into the existing behavior, only a description of the new behavior's bypass (which is not the same thing at all) > easy to bypass the cooling-off period with ADB I don't think this is a reasonable use of the term "easy". I should be able to give my non-technical friend an apk and they can use it right then, with the…

I will say, an underrated use case for even small, local LLMs is making command line tools drastically more accessible to laypeople I now know zero people I don't think should use linux, and people I know seems to run quite a gamut of technical know-how compared to most other technical folks I know

Having an LLM directly and autonomously drive command line tools outside of a strict sandbox sounds like a ticking time bomb.

Thinking tokens: "The files I'm trying to read are missing, I need to figure out why. I see the problem, I accidentally ran rm -rf /home/user. Let me run git restore. No that didn't work. Let me try git reset --hard origin/HEAD. That still didn't work. I should inform the user."

Output: "I was unable to complete the task you requested. Restore /home/user and I will try again"

Post reply on HN