merge mostly redundant FAQ section into future devices

Author: thestinger

static/faq.html

@@ -54,7 +54,6 @@ <h2><a href="#table-of-contents">Table of contents</a></h2>
                             <li><a href="#supported-devices">Which devices are supported?</a></li>
                             <li><a href="#recommended-devices">Which devices are recommended?</a></li>
                             <li><a href="#future-devices">Which devices will be supported in the future?</a></li>
-                            <li><a href="#when-devices">When will more devices be supported?</a></li>
                             <li><a href="#legacy-devices">Why are older devices no longer supported?</a></li>
                             <li><a href="#which-legacy-devices">Which devices did GrapheneOS support in the past?</a></li>
                             <li><a href="#device-lifetime">How long will GrapheneOS support my device for?</a></li>
@@ -346,34 +345,16 @@ <h3><a href="#future-devices">Which devices will be supported in the future?</a>
                     and dedicated towards it. Releases for each supported device need to be robust and
                     stable, with all standard functionality working properly and testing for each of the
                     releases.</p>
-                </article>
 
-                <article id="when-devices">
-                    <h3><a href="#when-devices">When will more devices be supported?</a></h3>
-
-                    <p>Broader device support can only happen after the community (companies,
-                    organizations and individuals) steps up to make substantial, ongoing contributions to
-                    making the existing device support sustainable. Once the existing device support is
-                    more sustainable, early research and development work for other devices can begin.
-                    Once a device is deemed to be a worthwhile target, the project needs maintainers to
-                    develop and maintain support for it including addressing device-specific issues that
-                    are uncovered, which will include issues uncovered in the device support code by
-                    GrapheneOS hardening features.</p>
-
-                    <p>It's not really a matter of time but rather a need for community support for the
-                    project increasing. As an open source project, the way to get something to happen in
-                    GrapheneOS is to contribute to it, and this is particularly true for device support
-                    since it's very self-contained and can be delegated to separate teams for each
-                    device. If you want to see more devices supported sooner, you should get to work on
-                    identifying good devices with full support for alternative operating systems with
-                    verified boot, etc. and then start working on integrating and testing support.</p>
-
-                    <p>It should also be clear that the expectation is for people to buy a device to run
-                    GrapheneOS, rather than GrapheneOS supporting their existing devices. This will only
-                    become more true if GrapheneOS is successful enough to accomplish the goal of having
-                    devices produced based on an SoC reference design with minor improvements for privacy
-                    and security. Broad device support is the opposite of what the project wants to
-                    achieve in the long term.</p>
+                    <p>The expectation is for people to buy a secure device meeting our requirements
+                    to run GrapheneOS. Broad device support would imply mainly supporting very badly
+                    secured devices unable to support our features. It would also take a substantial
+                    amount of resources away from our work on privacy and security, especially since
+                    a lot of it is closely tied to the hardware such as the USB-C port control and
+                    fixing or working around memory corruption bugs uncovered by our features. We
+                    plan to partner with OEMs to have devices produced meeting all our requirements,
+                    providing additional privacy/security features beyond them and ideally shipping
+                    with GrapheneOS rather than massively lowering our standards.</p>
                 </article>
 
                 <article id="legacy-devices">

static/js/redirect.js

@@ -23,6 +23,7 @@ const redirects = new Map([
     ["/usage#google-camera", "/usage#pixel-camera"],
 
     ["/faq#dns", "/faq#custom-dns"],
+    ["/faq#when-devices", "/faq#future-devices"],
 
     ["/hiring#qualitifations", "/hiring#qualifications"],