Live data from Hacker News

GrapheneOS Overhauled Default Apps and Secure Clipboard

grapheneos.social

191–200 of 284 posts

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#191
post #36

Earlier quoted context omitted.

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

I like Heliboard a lot, but its autocorrect gets stuck in the mud all the time. It completely falls apart and starts injecting nonsense phrases made up of nonsense misspelled words moment you miss a space ('v' or 'b') or type a really long word it doesn't know. It also stubbornly incorrects other things like 'a' into "and" if it thinks it knows a phrase fragment. It's always wrong. It just happened to me now twice .…

Autosuggestions are nice to have but there is no autocorrection that really works well in my experience regardless of OS.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#192

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.

FuriLabs makes a Linux phone that is designed as a daily driver. Looking at it to replace Android.

That's a huge downgrade for privacy, security, usability, battery life and compatibility with apps. GrapheneOS is Linux too. Linux doesn't mean glibc and systemd. Linux is unfortunately not a great base for an OS focused on privacy and security but it's the only practical choice at this time. In the long term, it needs to be replaced as the bare metal kernel.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#193

> RCS isn't an open platform in practice. It isn't even as open as SMS/MMS. It heavily depends on proprietary Google and carrier infrastructure in practice. We can start by replicating Google's approach and then we can work on only using carrier services for carriers where it's actually supported. What is the point of RCS though? It seems to be strictly inferior to Signal. It seems a Google product meant to serve Goo…

RCS allows higher resolution pictures than MMS.

RCS provides far better support for group chats, many small feature improvements and end-to-end encryption (E2EE) via Messaging Layer Security (MLS). E2EE for talking to GMS Android and iOS users without them needing to install another app is the main reason we care about it, but far better group chat support matters too. iPhone users very often don't want to have SMS/MMS users in their group chats.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#194

Earlier quoted context omitted.

I agree. The OS maker has a ton of power with the default apps and putting SMS and phone calls as the default communication platform of the OS is contrary to the goals of giving people more privacy. And the OS should come with a GrapheneOS Monero wallet to compete with Google Wallet/Apple Pay.

> And the OS should come with a GrapheneOS Monero wallet to compete with Google Wallet/Apple Pay. This makes no sense especially when you’re comparing it against Apple Pay and Google Wallet. They shouldn’t waste resources on something so pointless. The only exception is if they can actually make an NFC capable app that can handle cards.

A FOSS, private, uncensorable way to pay people instantly anywhere with effectively zero fees is not pointless.

Obviously it isn't a direct substitute for Apple pay but it would be more functionality than we have now.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#195

Earlier quoted context omitted.

One of the parties involved in a call recording it is not surveillance. It's comparable to having chat logs for text messaging. Contrary to what you've claimed, vast majority of US states have one party consent for call recording. GrapheneOS Foundation is based in Canada where one party consent is the law. Our feature is designed for people to comply with the law in jurisdictions requiring two party consent. It shows…

[flagged]

You've made multiple comments disparaging GrapheneOS because of two minor features it provides. Both features are fully legal for GrapheneOS to include. Both are legal to use as long as people follow applicable laws. Both our regular call recording and automatic call recording features display a prominent warning to users about following call recording consent laws. Proceeding requires accepting the dialog acknowledging the warning. Our implementation discourages people from violating laws and is fully legal itself.

There are other ways to record calls such as enabling speaker mode and using another device to record the audio. It's similar to apps trying to prevent users from taking screenshots. It fundamentally doesn't work.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#196
> In the longer term, we plan to add support for RCS including support for the standard end-to-end encryption (E2EE) via Messaging Layer Security (MLS). Currently, RCS including E2EE is available on GrapheneOS via Google Messages. We want to avoid the need to use Google Messages for RCS eventually.

Hell yeah. Google Messages has worked reasonably well for RCS so far (after a long and frustrating period where it didn't on T-Mobile), but having a non-Google option will be huge.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#197

Earlier quoted context omitted.

That cannot be true, when I install e.g., Ubuntu system, there are plenty of applications installed for me, with incompatible licenses.

Can you please elaborate on what you mean? Ubuntu does not aim to be a permissively-licensed system. It can include copyleft (e.g. GPL) and permissive (e.g. MIT) without issue. Permissively-licensed systems like FreeBSD and GrapheneOS cannot include GPL code if they want to remain permissive.

GrapheneOS does include GPLv2 code both via AOSP and our own but not GPLv3. We want GrapheneOS to have no additional restrictions beyond AOSP. AOSP uses GPLv2 but not GPLv3.

We do need to be careful with GPLv2 due to license incompatibilities. For example, GPLv2-only licensing such as the Linux kernel is incompatible with Apache 2 and GPLv3. GPLv3 is compatible with Apache 2 so GPLv2-or-later can be compatible but only by using it as GPLv3 with the extra restrictions too.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#198

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.

Why not Unexpected Keyboard?

As someone who uses and loves Unexpected Keyboard: the higher learning curve compared to other keyboards would be the main reason I can think of. The reliance on swipes in particular is something that's likely alien to a lot of smartphone users.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#199
post #31

Certainly, with Opus 5 and GPT-6, modernizing or even completely rewriting self-contained, non-critical tools seems like a Friday afternoon job now. I wonder however how important this is, in the grand scheme of things. I use GrapheneOS and the bundled messaging app is serviceable. It isn't pretty, but it gets the job done.

We're definitely not churning out code with AI models. There's no vibe coding going on in GrapheneOS. We're carefully writing and reviewing code as we've always done. We now have additional tools to assist with it. The main way we're using AI models is for code review and helping to write a lot more tests than we used to. It's helping to improve our code quality, not reducing it. We're not trying to get things done s…

I'm really glad to read this. Thanks for putting in the effort to make quality software, far too few people are willing to do that these days.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#200

> RCS isn't an open platform in practice. It isn't even as open as SMS/MMS. It heavily depends on proprietary Google and carrier infrastructure in practice. We can start by replicating Google's approach and then we can work on only using carrier services for carriers where it's actually supported. What is the point of RCS though? It seems to be strictly inferior to Signal. It seems a Google product meant to serve Goo…

It's nice to be able to send/receive photos with more than 13 pixels in them.
Post reply on HN