Live data from Hacker News

GrapheneOS Overhauled Default Apps and Secure Clipboard

grapheneos.social

281–284 of 284 posts

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#281

Earlier quoted context omitted.

Could you please elaborate? I wouldn't think this causes an issue unless they need to link against it, which I don't think they do.

Unsure what you mean by link against it. GPLv3 requires making the entire project it is bundled with GPLv3 as well. GrapheneOS would need to relicense the entire OS and bundled apps as GPLv3 to allow them to use any app with that license.

They mean linking as in [1] against a GPLv3 work to create a derived work. Simply including a GPLv3 application in a aggregation of different works (e.g. an OS image) does not require everything else to be GPLv3.

The GPLv3 only applies to a work and works derived from it, so either if you take an existing GPLv3 project and modify it or if you link against a GPLv3 project. In these cases, the other code needs to be under licenses that are compatible with the GPLv3.

This is clearly described in 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 compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

[1] https://en.wikipedia.org/wiki/Linker_(computing)

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#282
post #280

Earlier quoted context omitted.

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 runnin…

> There are enough instances now I will compile a list and email the moderators who can hopefully correct your behaviour

Thanks for taking the action. My posts questioning some aspects of Graphene also got flagged, not fairly in my opinion.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#283

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…

That's great but it's certainly not more secure than GrapheneOS against remote, local, or surveillance capitalism adversaries..

That duress pin idea is not good at all and would be bad for the users of GrapheneOS.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#284

Earlier quoted context omitted.

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…

That's great but it's certainly not more secure than GrapheneOS against remote, local, or surveillance capitalism adversaries.. That duress pin idea is not good at all and would be bad for the users of GrapheneOS.

That is a lack of imagination of what a _working phone_ as a false shell really is.

Not to want to give too much. Cell phone companies have no issue deactivating an account with a stated text message. Duress kernel can mimic it with other slight of hand displays that the _foot_ will accept as reality.

User lock down versus machine lock down moves to allowing the machine holes to be used for bypassing. User lock down allows for analyzing and patching the machine holes.

Post reply on HN