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

Devices with GrapheneOS support should be available in 2027

grapheneos.social

Post reply on HN
Print view View original

211–220 of 444 posts

Re: Devices with GrapheneOS support should be available in 2027

#211

Post by epihelix »

patall wrote: post #123
patall wrote: post #103

Earlier quoted context omitted.

Maybe that is possible in Germany. It is impossible here in Sweden. Or in other words: of course you can have mobile bankid without a smartphone, just use a tablet computer ;)

@fsflover: and my mobile phone provider. And my insurance. And my eletricity provider. And my housing associations customer portal. Getting doctors appointments. Mortgage. Union. National retirement savings account. Some of these may have some alternative left, but far too many you will be left out. Well, I can buy a train ticket without it, so I could still leave.

Do you mean to say that all these services require strong device integrity to function in Sweden?? In Australia, no local app that I'm aware of (banking, finance, government, medical) requires any form of device integrity - otherwise I couldn't use them. The only exception I've encountered is Google Wallet.

I wonder why there would be such a difference in policy between countries, not only in government but across the private sector? This doesn't make any sense to me. If anything, I'd expect Sweden to have a more sensible, left wing attitude than Oz.

Re: Devices with GrapheneOS support should be available in 2027

#212

Post by throwaway456754 »

steve_taylor wrote: post #92
RobotToaster wrote: post #87

Earlier quoted context omitted.

Not quite, they could make you request it by post and send it on a stack of floppies.

Sounds like a cheap way to get my hands on some floppies.

They don't have to be cheap.

Re: Devices with GrapheneOS support should be available in 2027

#213

Post by joelthelion »

J-Kuhn wrote: post #71
felooboolooomba wrote: post #55

[flagged]

Yeah, its the "well, legally, we have to provide the source code, but we make it as painful and slow for you as we can without it becoming a blatant violation of the GPL."

I'm pretty sure there is a lot of code in Android that belongs to Google and is not part of an upstream GPL project. They would be completely entitled to stop sharing it.

Re: Devices with GrapheneOS support should be available in 2027

#214

Post by limagnolia »

georgeecollins wrote: post #126
owaislone wrote: post #91

Earlier quoted context omitted.

Nothing is stopping you. You're free to use a desktop web app that either doesn't work or is terribly slow or has limited features on a mobile web browser. I'd love it if all apps were PWAs but that is not the case.

My broker has a much more fully featured web app then it does on iOS or Android. You can do things in a browser that the phone apps will send you to a browser to do. BofA is just as good of a web app. Maybe people are just used to using their phones?

Can you deposit checks from the webapp? That is the feature most often missing in banking webapps. It isn't something I need often, fortunately.

Re: Devices with GrapheneOS support should be available in 2027

#215

Post by zer00eyz »

smallmancontrov wrote: post #183
exceptione wrote: post #117

Earlier quoted context omitted.

There is a little bit of clumsiness in the way Google communicates with the public. What they really mean to say is: we need to be broken up.

I am in awe at the amount of capital Google's market dominance affords them and the consistency with which they squander that capital. https://killedbygoogle.com/ This is not the way.

Well.

Lest you forget that modern computing exists because ATT built unix and then threw it out to the public, at speed, as they drove away from it as fast as possible. (Something about being an actual monopoly...).

There is at least one thing, on that list that I can almost assure you will be coming back (in concept and spirt) in the next 5 years. Likely open source, because google tossed it...

Meanwhile it has other very public and open winners: Golang, Kubernetes being two stellar examples of them not dropping something like a hot potato.

Re: Devices with GrapheneOS support should be available in 2027

#216

Post by gf000 »

post-it wrote: post #60
geremiiah wrote: post #38

Earlier quoted context omitted.

I don't either. Don't we have free market capitalism? Why don't I have a Linux phone? And why do I need to worry that my government and banking apps won't work if I get a Linux phone?

Because you don't have capital.

well, apparently not even Microsoft had enough capital.

It's almost like the free market only works when we have well-defined and regulated markets. This has been known by Adam Smith and quite logical, yet people expect Google and Apple giga-corporations with monopolies to somehow abide by the laws of selling grains on the market.

Re: Devices with GrapheneOS support should be available in 2027

#219

Post by callc »

gruez wrote: post #208
teekert wrote: post #157

Earlier quoted context omitted.

At this point, without Git commit history (assuming it is a bare code dump), is it still even possible to guarantee it is what Google says it is?

You can compare against old dumps.

Sometimes I wonder if randos peek in and see this terminology and think we’re all nut cases

Re: Devices with GrapheneOS support should be available in 2027

#220

Post by stonogo »

FartyMcFarter wrote: post #190
felooboolooomba wrote: post #55

[flagged]

> Google, this small tech company (correct me if I'm wrong), is peddling source code via tarballs on google drive. What is the context for this? It's not clear from the linked social media post. The Android kernel source code is in git: https://android.googlesource.com/kernel/common/ Plus there's a lot of other Android source hosted on Google's git servers: https://android.googlesource.com/

The repositories you have linked are not sufficient to build an Android distribution. In order to get the missing bits, you have to fill out a form: https://source.android.com/opensourcerequest and beg them, and if they decide you are worthy, they will email you a link to a tarball, which is hosted on Google Drive.
Post reply on HN