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

271–280 of 284 posts

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#271

Post by wolvoleo »

grapheneos wrote: post #156
wolvoleo wrote: post #63

Earlier quoted context omitted.

They basically have opposite goals to Google so I don't imagine there will every be good feelings there. There shouldn't be. Yes Google wants android to be secure, but the problem is that to be truly secure it should be secure from Google too. And they don't want that. They want it to be their personal datamine and walled garden. Just like Apple with ios.

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

Google staff might follow you but their actions speak otherwise. Closing off AOSP, convincing OEMs to lock their bootloaders. They really want to consolidate control over Android.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#272

Post by Groxx »

microtonal wrote: post #222
kevin_thibedeau wrote: post #151

Earlier quoted context omitted.

Amazing how blinkered supposedly privacy conscious Europeans are when they willingly line up at the Facebook slaughterhouse.

The huge switch from SMS to WhatsApp in Europe was well done before they were acquired by Facebook. By then the damage was already done, because the network effects made it very hard to move away. By now, many people I know also have a Signal account, but it doesn't really get off the ground as long as, say, 30% of every group chat does not use Signal.

Year, back prior to the Zuckification I'd say it was a very clear upgrade for everyone in essentially every way. Dirt cheap (much less than even minimal texting), installable everywhere, adopted solid E2EE far ahead of basically every major player (2016!), it was great. USA had everything worse for a long time, and many things still are.

But once it landed in Zuck's hands, I no longer trust it one bit. Abandon ship.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#273

Post by fsflover »

ulrikrasmussen wrote: post #165
qurren wrote: post #68

Earlier quoted context omitted.

If they hard fork, a lot of apps that are generally "necessary for the average person" (e.g. Uber, banking apps, Gmail, Whatsapp/Wechat/Line) might stop working.

Yes, but there is no alternative other than giving up. Starting a new OS from scratch with zero apps is a much worse starting point compared to a platform where 99.9% of apps work (minus those relying on Play Integrity with strong integrity) which may have its rug pulled in the future. The race here is about getting to a big enough market share that GrapheneOS cannot just be ignored as completely niche but has to be…

> Yes, but there is no alternative other than giving up.

Of course there is. Sent from my daily driver Librem 5.

Disclaimer: It is less secure than GrapheneOS, according to the GrapheneOS threat model.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#274

Post by kasabali »

HybridStatAnim8 wrote: post #140
graemep wrote: post #23

Earlier quoted context omitted.

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.

That's textbook FUD.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#275

Post by xorcist »

novafunc wrote: post #75
gray_-_wolf wrote: post #44

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 cannot include GPL code if they want to remain permissive

It's hard to take this seriously when the entire kernel is GPL.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#276

Post by d3Xt3r »

yndoendo wrote: post #246
grapheneos wrote: post #192

Earlier quoted context omitted.

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.

Testing the FLX1S for a few weeks as a media player, modern day iPod tool with offline content storage / temp caching. Battery is better than current Android phone. Both have areas of better usability. I would recommend it as tool for a Linux app designer to use with testing and user improvement. Helps find issue not present on a laptop or desktop. Highlights the difference in solution choices; Python vs Node.js vs R…

This, 100%. It's exactly why I would choose a standard Linux distro any day over GrapheneOS. Biggest reasons for me being:

- No dependency on Google - Actually free and open OS (this means: root access to device, being able to customise any part of the distro/WM/DE, full, low-level access to external devices etc)

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#277

Post by mitxela »

grapheneos wrote: post #264
microtonal wrote: post #207

Earlier quoted context omitted.

Neither does the GPLv3: A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compila…

The issue isn't that GPLv3 applies to non-derivative OS components but rather that the terms apply to the overall redistribution of the OS. Including any GPLv3 component means GrapheneOS cannot be used in products where AOSP can be used due to having additional restrictions beyond GPLv2. We don't want more restrictive licensing than AOSP. We're fine with using additional GPLv2 code as long as we're sure it's not goin…

Name the restrictions.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#279

Post by wolvoleo »

terribleperson wrote: post #164
mitxela wrote: post #109

Earlier quoted context omitted.

Chrome is the outlier there. It didn't come with any desktop OS and still got near 100% market share, even before Android contributed to that. How? It's worth studying.

Well, the web was already designed to be compatible with multiple browsers, so that's one element there.

It wasn't really at that time. IE was really quirky and a lot of sites were tailored to those quirks and failed on standards-compliant browsers :S

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#280

Post by gib444 »

grapheneos wrote: post #249
gib444 wrote: post #214

Earlier quoted context omitted.

[flagged]

We've explained we're using a GrapheneOS project account due to libelous personal attacks, stalking and harassment towards our founder and other team members. Hacker News has many past threads filled with libelous personal attacks towards our team. We repeatedly asked for moderation intervention and it hasn't happened. We regularly had our replies in those threads flagged because it went against the bandwagon of hate…

You don't deny the flagging operation. Thanks for confirming it

More world salad to distract. No sources.

I'll send you some proof that my device is running GrapheneOS btw. How would you like to arrange that?

Yes my support of the project is variable, highly influenced by how it is run and how the directors act on social media. The project does not have a right not to be criticised and that includes the people running it. It's the flip side of the coin of engaging in a public forum

"HN is a community—users should have an identity that others can relate to" – it's not designed for corporate PR accounts. We all know it's you purely by your style of writing and persecution complex

Post reply on HN