diff options
Diffstat (limited to 'static/index.html')
| -rw-r--r-- | static/index.html | 18 |
1 files changed, 4 insertions, 14 deletions
diff --git a/static/index.html b/static/index.html index 60b4ee27..60b6e40f 100644 --- a/static/index.html +++ b/static/index.html @@ -26,7 +26,7 @@ <link rel="stylesheet" href="/grapheneos.css?29"/> <link rel="manifest" href="/manifest.webmanifest"/> <link rel="license" href="/LICENSE.txt"/> - <script type="module" src="/js/redirect.js?9"></script> + <script type="module" src="/js/redirect.js?10"></script> </head> <body> <header> @@ -183,19 +183,9 @@ <section id="upstream"> <h2><a href="#upstream">Upstream contributions</a></h2> - <p>GrapheneOS has made substantial contributions to the privacy and security of the - Android Open Source Project, along with contributions to the Linux kernel, LLVM, - OpenBSD and other projects. Much of our past work is no longer part of the downstream - GrapheneOS project because we've successfully landed many patches upstream. We've had - even more success with making suggestions and participating in design discussions to - steer things in the direction we want. Many upstream changes in AOSP such as removing - app access to low-level process, network, timing and profiling information originated - in the GrapheneOS project. The needs of the upstream projects are often different from - ours, so they'll often reimplement the features in a more flexible way. We've almost - always been able to move to using the upstream features and even when we still need - our own implementation it helps to have the concepts/restrictions considered by the - upstream project and apps needing to be compatible with it. Getting features upstream - often leads to an improved user experience and app compatibility.</p> + <p>See <a href="/faq#upstream">the FAQ section on our upstream work</a> improving + privacy and security for billions of users by getting a subset of our changes into + core infrastructure projects.</p> </section> <section id="copyright-and-licensing"> |