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

GrapheneOS Overhauled Default Apps and Secure Clipboard

grapheneos.social

Post reply on HN
Print view View original

131–140 of 284 posts

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#131

Post by HybridStatAnim8 »

GeekyBear wrote: post #93
tgsovlerkhgsel wrote: post #87

Earlier quoted context omitted.

There is no alternative. Apple isn't going to let them build on top of iOS, and anything except those two is dead in the water because it'll never have users because it is missing a bunch of critical apps, and will never have those apps because it doesn't have users.

> There is no alternative. There have been several projects like Ubuntu Touch to create an open Linux for smartphones. That would be an open alternative. Android is not open.

The AOSP is fully open source. What you suggest is a significant step back in terms of privacy and security.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#132

Post by HybridStatAnim8 »

ravenstine wrote: post #32

I hope they replace the AOSP keyboard with FUTO keyboard. I'm mostly fine with the other stock apps, but that keyboard was the one thing I absolutely had to end up replacing due to its jenky behavior.

They cannot. The license FUTO uses is not open source and is incompatible with being bundled with GrapheneOS.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#133

Post by HybridStatAnim8 »

mitxela wrote: post #110
idle_zealot wrote: post #64

Earlier quoted context omitted.

https://gitlab.futo.org/keyboard/latinime/-/blob/master/LICE... It is not open source. They use a custom source available license. There's no way any Android distribution would include it. A layman's reading is that FUTO could claim license violation on account of the distribution accepting donations (non-commercial use only) and there's a weird clause about not accusing FUTO of patent infringement.

Alternatively they could ask FUTO for a commercial license.

Maybe, but there are better candidates GrapheneOS is more interested in.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#134

Post by HybridStatAnim8 »

dsr_ wrote: post #36
ravenstine wrote: post #32

I hope they replace the AOSP keyboard with FUTO keyboard. I'm mostly fine with the other stock apps, but that keyboard was the one thing I absolutely had to end up replacing due to its jenky behavior.

Heliboard is good, customizable, and actually open source - GPL3.

If you are referring to Heliboard as an AOSP board replacement, that cannot work, GrapheneOS cannot use GPLv3 projects.

If you mean it as a user installed app, please disregard.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#135

Post by ticoombs »

aussieguy1234 wrote: post #58
goda90 wrote: post #12

I believe this is the planned gallery app. I've already been using it: https://github.com/IacobIonut01/ReFra

Just tried this out. I may soon be cancelling by Google Photos subscription...

While you're doing that check out Immich - https://immich.app

One of the best solutions I've ever used for photos, backups, enrichment, etc

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#136

Post by grapheneos »

NewJazz wrote: post #49
pizzaiolo wrote: post #37

Graphene is clearly bullish on Android, but I have no idea why. The writing is on the wall, Google is slowly asphyxiating AOSP.

Yes RCS is barely a standard worth implementing, let alone the best one. Make SMS/MMS and XMPP work together seamlessly in one app, forget RCS.

It's important for us to provide out-of-the-box end-to-end encrypted (E2EE) messaging for contacts on Google Messages and iOS. Both Google Messages and iOS provide RCS with end-to-end encryption via Messaging Layer Security (MLS). Google Messages is the standard text messaging app on Google Mobile Services Android and iOS now also supports RCS with MLS. The vast majority of people have an E2EE messaging app on their smartphone and it's important for us to provide compatibility with it. Currently, a growing number of our users are installing Google Messages to have better usability and privacy for texting with contacts on Google Messages and iOS.

People can already install the messaging apps of their choice on GrapheneOS. It would go against our approach to choose specific messaging apps and protocols to bundle with the OS beyond SMS/MMS/RCS. We shouldn't be the ones choosing Signal vs. SimpleX vs. Element or other options but rather that's up to users to decide. We need a messaging app to handle carrier-based messaging in the OS including providing end-to-end encryption for it and the rest is up to other open source developers.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#137

Post by HybridStatAnim8 »

0points wrote: post #69

[flagged]

What? The Messages overhaul has been going on in the background for months. They announced it near the end of the port rather than the start. What is wrong with that? It has nothing to do with AI.

You can check github and see this development has been going on for awhile.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#138

Post by grapheneos »

wolvoleo wrote: post #67
NewJazz wrote: post #49

Earlier quoted context omitted.

Yes RCS is barely a standard worth implementing, let alone the best one. Make SMS/MMS and XMPP work together seamlessly in one app, forget RCS.

Yes RCS is a pig with lipstick. Invented by the carriers to recoup some control over instant messaging, then abandoned and picked up by Google for the same reason. They're the ones that added encryption to it. It was always meant to be a walled garden. Exactly what an open system shouldn't be.

RCS is important because it provides end-to-end encryption (E2EE) for contacts with Google Messages and iOS. That means having E2EE for the vast majority of smartphone users since Google Messages is the standard GMS Android carrier-based messaging app.

https://news.ycombinator.com/item?id=49593026

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#139

Post by Cider9986 »

grapheneos wrote: post #126
Cider9986 wrote: post #38

Earlier quoted context omitted.

They are using AI [1]. I don't think messaging app is non-critical though. [1] https://github.com/GrapheneOS/Camera/tree/compose

Our port of Messaging to Compose was clearly not vibe coded as both the parent comment and yours are wrongly portraying it. Experienced developers have been working on overhauling the app for months with a lot of back and forth code review to get the pull requests into shape. We don't have a policy against using AI for assistance as long as the resulting code meets our high standards. We definitely use frontier AI mo…

How did my comment portray your port as you are vibecoding it? I just said that AI is being used.

It seems obvious to me that you guys would use it responsibly.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#140

Post by HybridStatAnim8 »

graemep wrote: post #23
HybridStatAnim8 wrote: post #17

Earlier quoted context omitted.

Their license is invalid due to being GPLv3. GPLv3 cannot be included in GrapheneOS as that would necessitate GrapheneOS give up their permissive licensing. Refra Gallery is licensed as Apache 2.0, which is a permissive license GrapheneOS can bundle in the OS.

Its not part of the OS so why would it affect the Graphene OS license? Its an app, not a library.

The Refra gallery fork would replace the current ancient gallery app. That would be bundled with the OS. Doing the same with the fossify suite or similar would be illegal. These licenses do not treat apps or libraries differently. GPLv3 code forces the code that it is bundled with to also be GPLv3.
Post reply on HN